Triple
T31963986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee House of Representatives District 70 |
E816123
|
entity |
| Predicate | electedOfficeTitle |
P36878
|
FINISHED |
| Object | State Representative |
—
|
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: State Representative | Statement: [Tennessee House of Representatives District 70, electedOfficeTitle, State Representative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electedOfficeTitle Context triple: [Tennessee House of Representatives District 70, electedOfficeTitle, State Representative]
-
A.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
B.
electedTitle
chosen
Indicates that an entity has been chosen through an election to hold a specific title or office.
-
C.
officeHolderTitle
Indicates the official position or title held by a person in an office or role.
-
D.
currentOfficeHolderTitle
Indicates the official title or position name held by the person who currently occupies a given office or role.
-
E.
residenceOfOfficeHolderTitle
Indicates the place where a person holding a particular official title resides while in that role.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 1, 2026, 12:09 a.m.