Triple
T16952137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim McDermott |
E411206
|
entity |
| Predicate | notableOfficeEnd |
P20778
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Jim McDermott, notableOfficeEnd, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOfficeEnd Context triple: [Jim McDermott, notableOfficeEnd, 2017]
-
A.
notableOfficeStatus
Indicates that an entity holds or has held a particularly significant or distinguished official position or office.
-
B.
notableOfficeStartContext
Indicates the contextual circumstances or conditions (such as time, place, or situation) surrounding the beginning of a notable office or position held by an entity.
-
C.
firstOfficeholderEnd
Indicates the point in time or event at which the tenure of the first officeholder in a given position or role comes to an end.
-
D.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
-
E.
notablePositionEnd
chosen
Indicates the point in time or event at which an entity’s notable position, role, or office comes to an end.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.