Triple
T35862046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontier County Board of Commissioners |
E1036978
|
entity |
| Predicate | isExecutiveBody |
P1001
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Frontier County Board of Commissioners, isExecutiveBody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExecutiveBody Context triple: [Frontier County Board of Commissioners, isExecutiveBody, true]
-
A.
executiveBody
chosen
Indicates that an entity serves as the executive governing authority or decision-making body for another entity.
-
B.
isElectedBody
Indicates that an entity is a formal decision-making group whose members attain their positions through an election process.
-
C.
isLegislativeBody
Indicates that the subject entity functions as an official law-making or legislative body within a political or organizational system.
-
D.
executiveBodyHoused
Indicates that an executive body is physically located or based within a particular building, facility, or premises.
-
E.
isClericalBodyFor
Indicates that one entity functions as the official clerical or administrative body responsible for serving, supporting, or governing another entity.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3883d48190b05e3d2da7a017ae |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.