Triple
T26932704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Posey County, Indiana |
E678276
|
entity |
| Predicate | locatedInCorner |
P26784
|
FINISHED |
| Object | southwestern corner of Indiana |
—
|
LITERAL 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: southwestern corner of Indiana | Statement: [Posey County, Indiana, locatedInCorner, southwestern corner of Indiana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCorner Context triple: [Posey County, Indiana, locatedInCorner, southwestern corner of Indiana]
-
A.
locatedAtCornerOf
chosen
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
B.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
C.
locatedOnFront
Indicates that one entity is positioned on the front side or face of another entity.
-
D.
cornerRole
Indicates the specific role or function an entity has in relation to a corner, such as positioning, responsibility, or interaction at that corner.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- F. None of above.
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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 27, 2026, 6:13 a.m.