Triple
T16153629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant County, Kentucky |
E391976
|
entity |
| Predicate | hasCountyJudgeExecutive |
P37263
|
FINISHED |
| Object | head of county government |
—
|
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: head of county government | Statement: [Grant County, Kentucky, hasCountyJudgeExecutive, head of county government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyJudgeExecutive Context triple: [Grant County, Kentucky, hasCountyJudgeExecutive, head of county government]
-
A.
hasCountyJudge
Indicates that a specified jurisdiction or administrative area is served or overseen by a particular county judge.
-
B.
hasCountyAdministrator
Indicates that an entity is administered or overseen by a specific county administrator.
-
C.
hasCountySheriff
Indicates that a jurisdiction or area is served or overseen by a specific county sheriff.
-
D.
countyExecutive
chosen
Indicates that one entity serves as the chief executive authority or leader for the government of the county represented by the other entity.
-
E.
hasCountyCommissioners
Indicates that an entity is governed or overseen by one or more county commissioners.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e57e95c8190ae4ed641be974ce5 |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.