Triple
T36562681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Expressway |
E901883
|
entity |
| Predicate | hasGradeSeparations |
P31430
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Oregon Expressway, hasGradeSeparations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGradeSeparations Context triple: [Oregon Expressway, hasGradeSeparations, yes]
-
A.
hasGradeSeparatedInterchanges
chosen
Indicates that the route or roadway includes interchanges where traffic flows are separated by different levels (e.g., overpasses/underpasses) rather than intersecting at the same grade.
-
B.
hasLaneSeparation
Indicates that there is a physical or marked separation between traffic lanes.
-
C.
hasGradeCrossings
Indicates that there are one or more level crossings where a road, path, or similar route intersects the railway or track at the same grade.
-
D.
gradeSeparationProject
Indicates a project whose purpose is to separate different transportation routes or levels (such as roads and railways) so they no longer intersect at the same grade.
-
E.
isDividedHighway
Indicates that a roadway consists of physically separated carriageways for opposing directions of traffic.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.