Triple
T12242052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayview, Missouri |
E291756
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | Mayview, MO |
E291756
|
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: Mayview, MO | Statement: [Mayview, Missouri, hasAbbreviation, Mayview, MO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mayview, MO Context triple: [Mayview, Missouri, hasAbbreviation, Mayview, MO]
-
A.
Mayview, Missouri
chosen
Mayview, Missouri is a small city located in Lafayette County in the western part of the state.
-
B.
Oakview, Missouri
Oakview, Missouri is a small suburban village in Clay County that forms part of the Kansas City metropolitan area.
-
C.
Centerview, Missouri
Centerview, Missouri is a small rural village located in Johnson County in the western part of the state.
-
D.
Auxvasse, Missouri
Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
-
E.
Fairview, Missouri
Fairview, Missouri is a small rural city in southwestern Missouri known for its agricultural surroundings and close-knit community.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cb59ce4819099999b8755fb8b98 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60ab5a404819089f9ea868deda10c |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.