Triple
T17504358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartholomew County, Indiana |
E426272
|
entity |
| Predicate | hasTown |
P847
|
FINISHED |
| Object | Clifford, Indiana |
—
|
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: Clifford, Indiana | Statement: [Bartholomew County, Indiana, hasTown, Clifford, Indiana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clifford, Indiana Context triple: [Bartholomew County, Indiana, hasTown, Clifford, Indiana]
-
A.
Clifford, Indiana
chosen
Clifford, Indiana is a small town located in the U.S. state of Indiana.
-
B.
Clayton, Indiana
Clayton, Indiana is a small town in central Indiana that forms part of the Indianapolis metropolitan area.
-
C.
Griffith, Indiana
Griffith, Indiana is a suburban town in northwest Indiana that forms part of the Chicago metropolitan area.
-
D.
Clarksville, Indiana
Clarksville, Indiana is a suburban town in southern Indiana along the Ohio River, known for its retail centers and proximity to Louisville, Kentucky.
-
E.
Crandall, Indiana
Crandall, Indiana is a small town located in Harrison County in the southern part of the U.S. state of Indiana.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45214d44c8190b1bf04bf24ab8e81 |
completed | April 19, 2026, 3:55 a.m. |
Created at: April 10, 2026, 5:48 a.m.