Triple
T15728258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubois County |
E381273
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | State of Indiana |
E32567
|
NE 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: State of Indiana | Statement: [Dubois County, partOf, State of Indiana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: State of Indiana Context triple: [Dubois County, partOf, State of Indiana]
-
A.
Hoosier State
The Hoosier State was a passenger train service that operated between Chicago, Illinois, and Indianapolis, Indiana, providing regional rail transportation in the Midwestern United States.
-
B.
Indiana
chosen
Indiana is a U.S. state known for its manufacturing base, rich agricultural land, and iconic events like the Indianapolis 500.
-
C.
Indiana
"Indiana" is a jazz standard widely performed and recorded by saxophonist Don Byas, showcasing his virtuosic improvisational style.
-
D.
Indiana and Kentucky
Indiana and Kentucky are neighboring U.S. states in the Midwest and Upper South, respectively, separated in large part by the Ohio River.
-
E.
Illinois and Indiana
Illinois and Indiana are neighboring Midwestern U.S. states whose shared boundary is partly defined by the Ohio River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb4cc0081909efe330339474017 |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9981e0d081909617b5d686905d3a |
completed | May 9, 2026, 8:30 p.m. |
Created at: April 10, 2026, 4:46 a.m.