Triple
T30810982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Reynolds |
E784643
|
entity |
| Predicate | roleAtHamptonCourtConference |
P4073
|
FINISHED |
| Object | Puritan spokesman |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Puritan spokesman | Statement: [John Reynolds, roleAtHamptonCourtConference, Puritan spokesman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtHamptonCourtConference Context triple: [John Reynolds, roleAtHamptonCourtConference, Puritan spokesman]
-
A.
conferenceHost
Indicates that an entity serves as the organizer or host responsible for running or managing a conference for another entity.
-
B.
MagicConference
Indicates that an event is a conference whose primary focus is on magic-related topics, activities, or discussions.
-
C.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
D.
associatedWithConference
Indicates that an entity has a connection or involvement with a specific conference, such as participation, organization, or affiliation.
-
E.
bookingRole
Indicates the role or capacity an entity has in relation to a booking (e.g., who made, manages, or is responsible for the booking).
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 29, 2026, 8:43 p.m.