Triple
T36431893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendell H. Ford |
E897465
|
entity |
| Predicate | termStartAsLieutenantGovernorOfKentucky |
P71683
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Wendell H. Ford, termStartAsLieutenantGovernorOfKentucky, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsLieutenantGovernorOfKentucky Context triple: [Wendell H. Ford, termStartAsLieutenantGovernorOfKentucky, 1967]
-
A.
startTimeAsGovernorOfKentuckyFirstTerm
Indicates the date and time when an individual’s first term serving as Governor of Kentucky began.
-
B.
startTimeAsLieutenantGovernor
chosen
Indicates the date and time at which an individual began serving in the role of lieutenant governor.
-
C.
endTimeAsGovernorOfKentuckyFirstTerm
Indicates the date and time when an individual's first term serving as Governor of Kentucky concludes.
-
D.
startTimeAsGovernorOfKentuckySecondTerm
Indicates the date and time when an individual began their second term serving as Governor of Kentucky.
-
E.
termStartAsGovernor
Indicates the date or point in time when an individual begins their term serving in the role of governor.
- 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.