Triple
T25878824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Sargent |
E651985
|
entity |
| Predicate | endOfNotableRole |
P20778
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Dick Sargent, endOfNotableRole, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfNotableRole Context triple: [Dick Sargent, endOfNotableRole, 1972]
-
A.
endOfNotableWork
Indicates the point in time or event at which a notable work is completed, concluded, or ceases to continue.
-
B.
notableHolderRole
Indicates that an entity is recognized for holding a particular role, office, or position in a notable or distinguished capacity.
-
C.
notablePositionEnd
chosen
Indicates the point in time or event at which an entity’s notable position, role, or office comes to an end.
-
D.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
-
E.
notableArcRole
Indicates that one entity holds a particularly important or prominent role within a narrative arc or storyline in relation to another entity.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6033b9dc48190b572786f332b939f |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 8:13 a.m.