Triple
T2967280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tip O'Neill |
E80194
|
entity |
| Predicate | officeEndForSpeaker |
P2941
|
FINISHED |
| Object | 1987-01-03 |
—
|
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-03 | Statement: [Tip O'Neill, officeEndForSpeaker, 1987-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeEndForSpeaker Context triple: [Tip O'Neill, officeEndForSpeaker, 1987-01-03]
-
A.
officeEnded
chosen
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
B.
recordingEnd
Indicates the point in time or event at which a recording process or recorded segment concludes.
-
C.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
-
D.
losingConference
Indicates that an entity is the conference in which another entity (typically a team or participant) is experiencing a losing or unsuccessful performance.
-
E.
spokeAt
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
- 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996e93788190ba9883714d4dfa0c |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.