Triple
T21315614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5th Street NW |
E525461
|
entity |
| Predicate | isMajorArteryIn |
P29360
|
FINISHED |
| Object | central Washington, D.C. |
—
|
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: central Washington, D.C. | Statement: [5th Street NW, isMajorArteryIn, central Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorArteryIn Context triple: [5th Street NW, isMajorArteryIn, central Washington, D.C.]
-
A.
isMajorArterialFor
Indicates that something functions as a primary high-capacity route or conduit serving as a main channel for movement, flow, or traffic for something else.
-
B.
isMajorRoadIn
chosen
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
hasArterialRoad
Indicates that one location or area is connected to or served by a major arterial road used for primary traffic flow.
-
D.
arterialRoad
Indicates that a road functions as a primary high-capacity route that channels major traffic flows between different areas of a transport network.
-
E.
vascularFeature
Indicates a relationship where one entity has, exhibits, or is characterized by a particular vascular structure or property.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75dcf2534819097abbb2e9559e791 |
completed | April 21, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:28 p.m.