Triple
T2097299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamar Alexander |
E37010
|
entity |
| Predicate | officeEndTime (Governor of Tennessee) |
P4346
|
FINISHED |
| Object | 1987-01-17 |
—
|
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: 1987-01-17 | Statement: [Lamar Alexander, officeEndTime (Governor of Tennessee), 1987-01-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeEndTime (Governor of Tennessee) Context triple: [Lamar Alexander, officeEndTime (Governor of Tennessee), 1987-01-17]
-
A.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
-
B.
currentGovernorStartDate
Indicates the date on which the entity’s current governorship officially began.
-
C.
officeholderEndTime
chosen
Indicates the time or date at which a person’s term in a particular office or position comes to an end.
-
D.
currentGovernor
Indicates that one entity is the person who presently holds the office of governor of the other entity.
-
E.
endTimeAsGovernorOfIndiana
Indicates the date and time at which an individual's tenure as Governor of Indiana concludes.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba9cb84481909fe0a66c020b8864 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.