Triple
T3822089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orrin Hatch |
E88595
|
entity |
| Predicate | startTime (president pro tempore) |
P13401
|
FINISHED |
| Object | 2015-01-06 |
—
|
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: 2015-01-06 | Statement: [Orrin Hatch, startTime (president pro tempore), 2015-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTime (president pro tempore) Context triple: [Orrin Hatch, startTime (president pro tempore), 2015-01-06]
-
A.
startTime (Senate Majority Leader)
Indicates the specific time at which the person serves or begins serving as Senate Majority Leader.
-
B.
startTime (U.S. Secretary of State)
Indicates the point in time when an individual began serving as U.S. Secretary of State.
-
C.
startTime (President of Poland)
Indicates the point in time at which a person begins serving as President of Poland.
-
D.
officeStartForPresident
Indicates the date or point in time when a person begins serving in the role of president.
-
E.
presidentProTempore
chosen
Indicates that one entity serves as the president pro tempore, i.e., the temporary or acting presiding officer, of a legislative or deliberative body associated with another entity.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.