Triple
T2086821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union County, Tennessee |
E45369
|
entity |
| Predicate | hasCountyMayor |
P185
|
FINISHED |
| Object | county mayor of Union County, Tennessee |
—
|
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: county mayor of Union County, Tennessee | Statement: [Union County, Tennessee, hasCountyMayor, county mayor of Union County, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyMayor Context triple: [Union County, Tennessee, hasCountyMayor, county mayor of Union County, Tennessee]
-
A.
hasMayor
chosen
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
-
B.
hasCountyAdministrator
Indicates that an entity is administered or overseen by a specific county administrator.
-
C.
hasCountySeatWithRole
Indicates that a county has a designated county seat that fulfills a specific administrative or governmental role.
-
D.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
E.
hasCityManager
Indicates that an entity has a specific individual who serves in the role of city manager for it.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba5641208190b925676b8d80f300 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.