Triple
T31845905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Lady of Tennessee |
E812938
|
entity |
| Predicate | successorTitlePattern |
P199019
|
FINISHED |
| Object | First Lady of [next governor] |
—
|
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: First Lady of [next governor] | Statement: [First Lady of Tennessee, successorTitlePattern, First Lady of [next governor]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitlePattern Context triple: [First Lady of Tennessee, successorTitlePattern, First Lady of [next governor]]
-
A.
successorTitle
Indicates the title or position that directly follows and replaces a previous one in a sequence or succession.
-
B.
successorTitleContext
Indicates the contextual circumstances or framework under which one title succeeds another.
-
C.
predecessorTitlePattern
Indicates the pattern or template used to represent the title of an entity’s immediate predecessor in a sequence or hierarchy.
-
D.
successorTitlePossible
Indicates that a particular title is eligible or allowed to be used as the successor to another title.
-
E.
successorTitleLocation
Indicates the location or context in which a successor’s title or position is held or applies.
- F. None of above. chosen
Provenance (4 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69ff1ba7494481908678a7a0f93dbd03 |
completed | May 9, 2026, 11:33 a.m. |
Created at: April 30, 2026, 11:50 p.m.