Triple
T7413686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Levi P. Morton |
E171074
|
entity |
| Predicate | startTimeVicePresidency |
P10270
|
FINISHED |
| Object | 1889 |
—
|
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: 1889 | Statement: [Levi P. Morton, startTimeVicePresidency, 1889]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeVicePresidency Context triple: [Levi P. Morton, startTimeVicePresidency, 1889]
-
A.
termStartAsVicePresident
chosen
Indicates that an entity begins its term in office holding the position of vice president.
-
B.
startTimeAsECPresident
Indicates the point in time at which an individual begins their term serving as President of the European Commission.
-
C.
servesAsVicePresidentDuring
Indicates that one entity holds the position of vice president for another entity during a specified time period.
-
D.
presidentDuringVicePresidency
Indicates that one person served as president during the period when another person was serving as vice president.
-
E.
officeStartTime (Vice President of the United States)
Indicates the date and time at which a person begins serving in the role of Vice President of the United States.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c336308190932c14cec5eec25f |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.