Triple
T33526957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chelsea, Oklahoma |
E858664
|
entity |
| Predicate | roadPassesNear |
P30397
|
FINISHED |
| Object | U.S. Route 66 underpass |
—
|
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: U.S. Route 66 underpass | Statement: [Chelsea, Oklahoma, roadPassesNear, U.S. Route 66 underpass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadPassesNear Context triple: [Chelsea, Oklahoma, roadPassesNear, U.S. Route 66 underpass]
-
A.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
B.
roadTraverses
chosen
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
C.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
D.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
E.
roadAccessArea
Indicates that an area is designated for or provides access to a road, such as for entry, exit, or connection.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.