Triple
T2967279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tip O'Neill |
E80194
|
entity |
| Predicate | officeStartForSpeaker |
P12495
|
FINISHED |
| Object | 1977-01-04 |
—
|
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: 1977-01-04 | Statement: [Tip O'Neill, officeStartForSpeaker, 1977-01-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartForSpeaker Context triple: [Tip O'Neill, officeStartForSpeaker, 1977-01-04]
-
A.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
B.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
-
C.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
D.
officeStartForPresident
Indicates the date or point in time when a person begins serving in the role of president.
-
E.
termStartAsSpeaker
chosen
Indicates that an entity begins serving or acting in the role of a speaker at the start of a specified term or period.
- 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.