Triple
T25101233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smithton, Missouri |
E628727
|
entity |
| Predicate | nearbyRegionalCenter |
P84435
|
FINISHED |
| Object | Columbia, 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: Columbia, Missouri | Statement: [Smithton, Missouri, nearbyRegionalCenter, Columbia, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyRegionalCenter Context triple: [Smithton, Missouri, nearbyRegionalCenter, Columbia, Missouri]
-
A.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
C.
hasRegionalCenterNearby
chosen
Indicates that a regional center is located in close proximity to the referenced entity.
-
D.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
E.
nearbyRegionCharacterizedBy
Indicates that a region located nearby another entity is defined or distinguished by a particular characteristic, feature, or condition.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 6:25 a.m.