Triple
T1158995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pete Rouse |
E24451
|
entity |
| Predicate | officeLeftDate |
P171
|
FINISHED |
| Object | 2011-01-13 |
—
|
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: 2011-01-13 | Statement: [Pete Rouse, officeLeftDate, 2011-01-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeLeftDate Context triple: [Pete Rouse, officeLeftDate, 2011-01-13]
-
A.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
B.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
C.
leftOffice
chosen
Indicates that an entity ceased holding or performing the duties of a particular office or position.
-
D.
officeInvolved
Indicates that a particular office or organizational unit is involved or participates in a specified event, action, or relationship.
-
E.
appointedOn
Indicates the specific date or time at which an entity is formally assigned or designated to a role, position, or responsibility.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcad47a08190895769611798f67f |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.