Triple
T17329107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pike County, Indiana |
E420765
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object |
Stendal, Indiana
Stendal, Indiana is a small unincorporated rural community located in Pike County in southwestern Indiana.
|
E1262695
|
NE FINISHED |
How this triple was built (4 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: Stendal, Indiana | Statement: [Pike County, Indiana, hasSettlement, Stendal, Indiana]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stendal, Indiana Context triple: [Pike County, Indiana, hasSettlement, Stendal, Indiana]
-
A.
Stinesville, Indiana
Stinesville, Indiana is a small historic town in Monroe County known for its limestone quarrying heritage.
-
B.
Stilesville, Indiana
Stilesville, Indiana is a small town located in Hendricks County in the U.S. state of Indiana.
-
C.
Haubstadt, Indiana
Haubstadt, Indiana is a small town in southwestern Indiana known for its rural community character and proximity to the Evansville metropolitan area.
-
D.
Kennard, Indiana
Kennard, Indiana is a small rural town located in Henry County in the central part of the U.S. state of Indiana.
-
E.
Oldenburg, Indiana
Oldenburg, Indiana is a small town in southeastern Indiana known for its strong German heritage, historic architecture, and numerous religious institutions.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Stendal, Indiana Triple: [Pike County, Indiana, hasSettlement, Stendal, Indiana]
Generated description
Stendal, Indiana is a small unincorporated rural community located in Pike County in southwestern Indiana.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Stendal, Indiana Target entity description: Stendal, Indiana is a small unincorporated rural community located in Pike County in southwestern Indiana.
-
A.
Stinesville, Indiana
Stinesville, Indiana is a small historic town in Monroe County known for its limestone quarrying heritage.
-
B.
Stilesville, Indiana
Stilesville, Indiana is a small town located in Hendricks County in the U.S. state of Indiana.
-
C.
Haubstadt, Indiana
Haubstadt, Indiana is a small town in southwestern Indiana known for its rural community character and proximity to the Evansville metropolitan area.
-
D.
Kennard, Indiana
Kennard, Indiana is a small rural town located in Henry County in the central part of the U.S. state of Indiana.
-
E.
Oldenburg, Indiana
Oldenburg, Indiana is a small town in southeastern Indiana known for its strong German heritage, historic architecture, and numerous religious institutions.
- F. None of above. chosen
Provenance (5 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d50b308190a255874a9b8f3cd3 |
completed | April 19, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c4dff088190833122dbe2981045 |
completed | May 11, 2026, 7:59 a.m. |
| NEDg | Description generation | batch_6a018eecff38819092c801e4c9d3a8a0 |
completed | May 11, 2026, 8:10 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a018f50002c8190ae2457cefabacbbe |
completed | May 11, 2026, 8:12 a.m. |
Created at: April 10, 2026, 5:43 a.m.