Triple
T1378034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glenview, Illinois |
E29269
|
entity |
| Predicate | directionFromChicago |
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: [Glenview, Illinois, directionFromChicago, northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromChicago Context triple: [Glenview, Illinois, directionFromChicago, northwest]
-
A.
directionFromBoston
Indicates the compass direction or bearing of one location as measured outward from Boston.
-
B.
distanceFromChicagoLoop
Indicates the spatial distance between an entity’s location and the Chicago Loop area.
-
C.
distanceToChicagoLoop
Indicates the spatial distance between a given location and Chicago’s central business district (the Loop).
-
D.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
E.
directionFromLondon
Indicates the cardinal or relative compass direction of an entity’s location when measured from London.
- 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_69a498d883a48190bfdca525296ef7ee |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c3173548819082aec7c1af9c577c |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:59 p.m.