Triple
T23601198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 95 bridge over Occoquan River |
E582761
|
entity |
| Predicate | isPartOfCorridorBetween |
P85888
|
FINISHED |
| Object | Washington, D.C. |
—
|
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: Washington, D.C. | Statement: [Interstate 95 bridge over Occoquan River, isPartOfCorridorBetween, Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfCorridorBetween Context triple: [Interstate 95 bridge over Occoquan River, isPartOfCorridorBetween, Washington, D.C.]
-
A.
onCorridorBetween
Indicates that one entity is located along the corridor that lies between two other reference entities or areas.
-
B.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
C.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
D.
locatedInTravelDirectionCorridor
Indicates that something is positioned within a corridor that lies along the direction of travel.
-
E.
isStopOnCorridor
Indicates that a location functions as a designated stop situated along a corridor or 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_69e248faa2788190abb1581742daa6aa |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0936f588190aead4419aedfcb0e |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.