Triple
T31526174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wheaton-Glenmont area |
E804347
|
entity |
| Predicate | metroLineTerminusFor |
P151408
|
FINISHED |
| Object | Washington Metro Red Line |
—
|
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 Metro Red Line | Statement: [Wheaton-Glenmont area, metroLineTerminusFor, Washington Metro Red Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metroLineTerminusFor Context triple: [Wheaton-Glenmont area, metroLineTerminusFor, Washington Metro Red Line]
-
A.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
-
B.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
railTerminusFor
chosen
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
-
E.
lightRailNetworkEndpointFor
Indicates that one entity serves as an endpoint (such as a terminus or boundary station) of a specified light rail network.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:58 p.m.