Triple
T23020968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshall County, Kentucky |
E573161
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Hardin, 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: Hardin, Kentucky | Statement: [Marshall County, Kentucky, hasCity, Hardin, Kentucky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hardin, Kentucky Context triple: [Marshall County, Kentucky, hasCity, Hardin, Kentucky]
-
A.
Hardin, Kentucky
chosen
Hardin, Kentucky is a small rural city located in Marshall County in western Kentucky.
-
B.
Crittenden, Kentucky
Crittenden, Kentucky is a small city in northern Kentucky that serves as a residential community within the Cincinnati metropolitan area.
-
C.
Hardinsburg, Kentucky
Hardinsburg, Kentucky is a small city in north-central Kentucky known as the administrative and commercial hub of Breckinridge County.
-
D.
Shreve, Kentucky
Shreve, Kentucky is a small unincorporated community located in Ohio County in the western part of the U.S. state of Kentucky.
-
E.
Harlan, Kentucky
Harlan, Kentucky is a small city in southeastern Kentucky known historically as a coal-mining community in the Appalachian region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183e9208081908fdbb8e21cacedde |
completed | April 29, 2026, 4:07 a.m. |
Created at: April 17, 2026, 3:52 p.m.