Triple
T8526110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garden City, Missouri |
E201821
|
entity |
| Predicate | isLocatedInDirectionFromKansasCity |
P83151
|
FINISHED |
| Object | southeast vicinity |
—
|
LITERAL 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: southeast vicinity | Statement: [Garden City, Missouri, isLocatedInDirectionFromKansasCity, southeast vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedInDirectionFromKansasCity Context triple: [Garden City, Missouri, isLocatedInDirectionFromKansasCity, southeast vicinity]
-
A.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
-
B.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
-
C.
geographicDirectionWithinState
Indicates that one location lies in a specified cardinal or relative geographic direction within the boundaries of a particular state.
-
D.
directionFromChicago
Indicates the cardinal or relative compass direction of an entity’s location measured from Chicago.
-
E.
directionFromWashingtonDC
Indicates the cardinal or relative compass direction of one place or object as measured from Washington, D.C.
- F. None of above. chosen
Provenance (4 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6463fe48190b6d3482212356be1 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.