Triple
T24127065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle County, Kentucky |
E597830
|
entity |
| Predicate | isNamedCountyOf |
P154947
|
FINISHED |
| Object | Kentucky |
—
|
NE NERFINISHED |
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: Kentucky | Statement: [Carlisle County, Kentucky, isNamedCountyOf, Kentucky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNamedCountyOf Context triple: [Carlisle County, Kentucky, isNamedCountyOf, Kentucky]
-
A.
isCornerCountyOf
Indicates that a county lies at or near the corner where two or more larger administrative regions (such as states or districts) meet.
-
B.
isInCountySeatOf
Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
-
C.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
-
D.
hasCountySeatOfParentCounty
Indicates that a location serves as the county seat (administrative center) for the county that is the parent of another referenced entity.
-
E.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df740a508190a80af01d99000127 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 11:19 p.m.