Triple
T27336304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stotts City, Missouri |
E689959
|
entity |
| Predicate | isLocatedInTheSouthwesternPartOf |
P147508
|
FINISHED |
| Object | Missouri |
—
|
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: Missouri | Statement: [Stotts City, Missouri, isLocatedInTheSouthwesternPartOf, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInTheSouthwesternPartOf Context triple: [Stotts City, Missouri, isLocatedInTheSouthwesternPartOf, Missouri]
-
A.
locatedInSouthwesternPartOf
chosen
Indicates that one entity is situated within the southwestern portion or region of another entity.
-
B.
locatedSouthWestOf
Indicates that one entity is positioned to the southwest of another entity, combining both a southern and western relative location.
-
C.
isSouthwesternEndpointOf
Indicates that an entity serves as the southwestern end or terminal point of another entity (such as a route, boundary, or segment).
-
D.
locatedInTheSouthernPartOf
Indicates that one entity is situated within the southern portion or region of another entity.
-
E.
isSouthernmostPartOf
Indicates that one entity is the geographically furthest south portion or section 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_69ef355e5b388190a8fc1eba9b4a6656 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 11:40 a.m.