Triple
T4592253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota Avenue station |
E103519
|
entity |
| Predicate | servesRiver |
P5565
|
FINISHED |
| Object | Anacostia River vicinity |
—
|
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: Anacostia River vicinity | Statement: [Minnesota Avenue station, servesRiver, Anacostia River vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRiver Context triple: [Minnesota Avenue station, servesRiver, Anacostia River vicinity]
-
A.
waterwayServed
chosen
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
B.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
C.
runOfTheRiver
Indicates a relationship where a hydroelectric facility operates using the natural flow and elevation drop of a river without significant water storage or regulation by a large reservoir.
-
D.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
E.
majorPortOnRiver
Indicates that a port is a primary or significant harbor facility located on the banks of a specified river.
- 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_69bd43dccaf08190aa89e9991a289719 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd592520ec8190b1bd4cb4d9b94c94 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:11 p.m.