Triple
T3471492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gladstone, Missouri |
E73268
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Claycomo, Missouri |
E75875
|
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: Claycomo, Missouri | Statement: [Gladstone, Missouri, borders, Claycomo, Missouri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Claycomo, Missouri Context triple: [Gladstone, Missouri, borders, Claycomo, Missouri]
-
A.
Claycomo, Missouri
chosen
Claycomo, Missouri is a small suburban village in the Kansas City metropolitan area known primarily for its Ford Motor Company assembly plant.
-
B.
Elkhorn, Missouri
Elkhorn, Missouri is a small unincorporated rural community located in Ray County in the U.S. state of Missouri.
-
C.
Bellamy, Missouri
Bellamy, Missouri is a small unincorporated community located in rural Vernon County in the western part of the state.
-
D.
Levasy, Missouri
Levasy, Missouri is a small rural city located in eastern Jackson County within the Kansas City metropolitan area.
-
E.
Sarcoxie, Missouri
Sarcoxie, Missouri is a small historic city in southwestern Missouri known for its agricultural roots and role as a local community hub in Jasper County.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb3af0cc81909e575828caeaeae0 |
completed | March 8, 2026, 6:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b36810958c81908982e0ef996dc480 |
completed | March 13, 2026, 1:27 a.m. |
Created at: March 8, 2026, 3:17 p.m.