Triple
T8206700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sevier |
E191704
|
entity |
| Predicate | termStartAsGovernorOfTennessee |
P25420
|
FINISHED |
| Object | 1796 |
—
|
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: 1796 | Statement: [John Sevier, termStartAsGovernorOfTennessee, 1796]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsGovernorOfTennessee Context triple: [John Sevier, termStartAsGovernorOfTennessee, 1796]
-
A.
termStartAsGovernor
chosen
Indicates the date or point in time when an individual begins their term serving in the role of governor.
-
B.
startTimeAsGovernorOfKentuckyFirstTerm
Indicates the date and time when an individual’s first term serving as Governor of Kentucky began.
-
C.
endTimeAsGovernorOfKentuckyFirstTerm
Indicates the date and time when an individual's first term serving as Governor of Kentucky concludes.
-
D.
termStartAsActingGovernor
Indicates that a person’s term in office began while they were serving in the capacity of an acting governor rather than as a fully appointed or elected governor.
-
E.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb726b520081908ce4a03bd14dfcdf |
completed | March 31, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:43 p.m.