Triple
T543228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon County, Florida |
E12676
|
entity |
| Predicate | hasCountyCommissioners |
P15485
|
FINISHED |
| Object | elected officials |
—
|
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: elected officials | Statement: [Leon County, Florida, hasCountyCommissioners, elected officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyCommissioners Context triple: [Leon County, Florida, hasCountyCommissioners, elected officials]
-
A.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
B.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
C.
hasRegionalCommission
Indicates that an entity is associated with, overseen by, or falls under the jurisdiction of a specific regional commission.
-
D.
hasCountySeatFunction
Indicates that an entity serves as the official county seat, functioning as the administrative center for a county.
-
E.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4986250508190ac91cfdf7d57073d |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b8098481908097228db8ad0262 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.