Triple
T987764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 435 |
E21316
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Gladstone, Missouri |
E73268
|
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: Gladstone, Missouri | Statement: [Interstate 435, passesThrough, Gladstone, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gladstone, Missouri Context triple: [Interstate 435, passesThrough, Gladstone, Missouri]
-
A.
Gladstone, Missouri
chosen
Gladstone, Missouri is a suburban city in the Kansas City metropolitan area known for its residential neighborhoods and community-oriented services.
-
B.
Sibley, Missouri
Sibley, Missouri is a small village in western Missouri known for its proximity to the historic Fort Osage site along the Missouri River.
-
C.
Oakview, Missouri
Oakview, Missouri is a small suburban village in Clay County that forms part of the Kansas City metropolitan area.
-
D.
Greenwood, Missouri
Greenwood, Missouri is a small suburban city in the Kansas City metropolitan area located in Jackson County in western Missouri.
-
E.
Levasy, Missouri
Levasy, Missouri is a small rural city located in eastern Jackson County within the Kansas City metropolitan area.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4a89a58819081a24b5b0a12f122 |
completed | March 1, 2026, 9:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad013e770c8190a97a67d546da341a |
completed | March 8, 2026, 4:55 a.m. |
Created at: March 1, 2026, 7:41 p.m.