Triple
T26383817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montezuma, Missouri |
E663218
|
entity |
| Predicate | isInU.S._state |
P31574
|
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: [Montezuma, Missouri, isInU.S._state, Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInU.S._state Context triple: [Montezuma, Missouri, isInU.S._state, Missouri]
-
A.
isInUSState
chosen
Indicates that one entity (typically a place or location) is geographically located within the boundaries of a specific U.S. state.
-
B.
isInUnitedStates
Indicates that one entity is located within the geographic or political boundaries of the United States.
-
C.
isInUnitedStatesMunicipalHierarchy
Indicates that one administrative or governmental unit occupies a specific level or position within the municipal hierarchy of the United States (e.g., city, town, county, or similar local jurisdiction).
-
D.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
E.
hasStateOrDistrict
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610779e3481909bda4d2b1c5c4cb0 |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:20 p.m.