Triple
T4973638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Schley |
E111711
|
entity |
| Predicate | termStartAsGovernorOfGeorgia |
P25420
|
FINISHED |
| Object | 1835 |
—
|
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: 1835 | Statement: [William Schley, termStartAsGovernorOfGeorgia, 1835]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termStartAsGovernorOfGeorgia Context triple: [William Schley, termStartAsGovernorOfGeorgia, 1835]
-
A.
termStartAsGovernor
chosen
Indicates the date or point in time when an individual begins their term serving in the role of governor.
-
B.
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.
-
C.
currentGovernorStartDate
Indicates the date on which the entity’s current governorship officially began.
-
D.
servedAsGovernorUntil
Indicates that an entity held the position of governor up to a specified end date or time.
-
E.
startTimeAsGovernorOfKentuckyFirstTerm
Indicates the date and time when an individual’s first term serving as Governor of Kentucky began.
- 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_69bd441a0eb481908050fa4273b19eae |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd7146e6e881908a55ab2756b631f6 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:33 p.m.