Triple
T8956602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kildeer, Illinois |
E213485
|
entity |
| Predicate | locatedInDirectionFromChicago |
P27124
|
FINISHED |
| Object | northwest |
—
|
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: northwest | Statement: [Kildeer, Illinois, locatedInDirectionFromChicago, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDirectionFromChicago Context triple: [Kildeer, Illinois, locatedInDirectionFromChicago, northwest]
-
A.
directionFromChicago
chosen
Indicates the cardinal or relative compass direction of an entity’s location measured from Chicago.
-
B.
isLocatedInDirectionFromKansasCity
Indicates that one place is situated in a specific cardinal or relative direction from Kansas City.
-
C.
locatedInDirectionFromNYC
Indicates that one place is situated in a specified compass direction relative to New York City.
-
D.
distanceFromChicagoLoop
Indicates the spatial distance between an entity’s location and the Chicago Loop area.
-
E.
distanceFromChicagoUnionStation
Indicates the measured distance between a given location and Chicago Union Station.
- 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_69ca8399ad2081909f8fa41d4314c215 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6728965881908e9f14aaee0c5a18 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7 p.m.