Triple
T35391465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Heights |
E1022949
|
entity |
| Predicate | hasNearbyMetrorailLine |
P17559
|
FINISHED |
| Object | Green Line of the Washington Metro |
—
|
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: Green Line of the Washington Metro | Statement: [District Heights, hasNearbyMetrorailLine, Green Line of the Washington Metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMetrorailLine Context triple: [District Heights, hasNearbyMetrorailLine, Green Line of the Washington Metro]
-
A.
hasNearbyOvergroundLine
Indicates that one entity is located close to an above-ground railway or transit line associated with the other entity.
-
B.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
-
C.
nearestCommuterRailLine
Indicates the commuter rail line that is geographically closest to a given location or entity.
-
D.
hasMetroLine
chosen
Indicates that a location or area is served by, or connected to, a specific metro (subway) line.
-
E.
hasSubwayLineAboveOrBelow
Indicates that one subway line is physically located above or below another subway line, such as on different levels of a transit system.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: May 3, 2026, 4:03 p.m.