Triple
T33535206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnside Street |
E858901
|
entity |
| Predicate | isMajorTrafficCorridorFor |
P175217
|
FINISHED |
| Object | central Portland |
—
|
NE NERFINISHED |
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: central Portland | Statement: [Burnside Street, isMajorTrafficCorridorFor, central Portland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTrafficCorridorFor Context triple: [Burnside Street, isMajorTrafficCorridorFor, central Portland]
-
A.
isMajorTrafficRoute
chosen
Indicates that a road or pathway serves as a primary, heavily used route for traffic flow within a transportation network.
-
B.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
majorTransportCorridor
Indicates that a route or pathway functions as a primary, high-capacity channel for transporting people or goods between significant locations.
-
D.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
E.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 1:39 a.m.