Triple
T19187472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Daye |
E469741
|
entity |
| Predicate | Matthew DayeRole |
P134784
|
FINISHED |
| Object | step-son and assistant printer |
—
|
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: step-son and assistant printer | Statement: [Stephen Daye, Matthew DayeRole, step-son and assistant printer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Matthew DayeRole Context triple: [Stephen Daye, Matthew DayeRole, step-son and assistant printer]
-
A.
James Pearson
Indicates a relationship or action involving the entity named "James Pearson" and another entity, event, or attribute, depending on context.
-
B.
Brian NiccolRole
Indicates that a specified role or position is held by, associated with, or pertains to Brian Niccol.
-
C.
Kevin P. RyanRole
Indicates the specific role, position, or capacity associated with Kevin P. Ryan in a given context.
-
D.
RobMorrowRole
Indicates that a person has played a specific role in a work featuring Rob Morrow.
-
E.
Dan HartRole
Indicates that Dan Hart holds or performs a specific role, position, or function in relation to another entity or context.
- F. None of above. chosen
Provenance (4 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f89f3ebc8190ba01ae075ffc77df |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.