Triple
T1544876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward 1 of Washington, D.C. |
E32953
|
entity |
| Predicate | hasMajorCorridor |
P5520
|
FINISHED |
| Object | 14th Street NW |
—
|
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: 14th Street NW | Statement: [Ward 1 of Washington, D.C., hasMajorCorridor, 14th Street NW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCorridor Context triple: [Ward 1 of Washington, D.C., hasMajorCorridor, 14th Street NW]
-
A.
hasMajorRailCorridor
Indicates that a location or region is traversed by a primary, high-capacity railway route used for significant passenger or freight transport.
-
B.
hasMajorHighway
Indicates that a location or area is served by or directly connected to a major highway route.
-
C.
hasMajorCrossing
Indicates that one entity has a significant or primary intersection or crossing with another entity.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
hasCorridor
chosen
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.