Triple
T5781716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivers Casino Des Plaines |
E127572
|
entity |
| Predicate | proximityToHighway |
P49834
|
FINISHED |
| Object | near Interstate 294 |
—
|
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: near Interstate 294 | Statement: [Rivers Casino Des Plaines, proximityToHighway, near Interstate 294]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToHighway Context triple: [Rivers Casino Des Plaines, proximityToHighway, near Interstate 294]
-
A.
approximateDistanceFromHighway1
Indicates the estimated distance between a location and Highway 1, rather than an exact measured value.
-
B.
connectsToHighway
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
C.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
nearbyMajorRoad
chosen
Indicates that one entity is located close to a significant or heavily used road.
-
E.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
- 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_69c008361fa88190aefa4dc41b051e7f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a17315881908aa12a830ba5f22b |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.