Triple
T30833532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest street naming system of Washington, D.C. |
E785293
|
entity |
| Predicate | includesDiagonalAvenues |
P202655
|
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: [Northwest street naming system of Washington, D.C., includesDiagonalAvenues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDiagonalAvenues Context triple: [Northwest street naming system of Washington, D.C., includesDiagonalAvenues, yes]
-
A.
avenueRadiatingFrom
Indicates that one avenue extends outward from and is oriented away from another central point or thoroughfare, like a spoke radiating from a hub.
-
B.
hasCrossStreets
Indicates that a location is situated at or near the intersection of the specified streets.
-
C.
roadCorridorIncludes
Indicates that a specified road corridor spatially contains or encompasses another element or segment within its defined bounds.
-
D.
isOnArcherAvenue
Indicates that one entity is located on or along Archer Avenue.
-
E.
isDowntownAxis
Indicates that something serves as or lies along the main central axis of a downtown area.
- F. None of above. chosen
Provenance (4 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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_6a00a74afb3c8190a274bf6681950aa3 |
completed | May 10, 2026, 3:42 p.m. |
Created at: April 29, 2026, 8:45 p.m.