Triple
T23902890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veirs Mill Road |
E601100
|
entity |
| Predicate | connectsToTransit |
P69365
|
FINISHED |
| Object | Wheaton Metro station vicinity |
—
|
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: Wheaton Metro station vicinity | Statement: [Veirs Mill Road, connectsToTransit, Wheaton Metro station vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToTransit Context triple: [Veirs Mill Road, connectsToTransit, Wheaton Metro station vicinity]
-
A.
hasTransitAccessTo
chosen
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
B.
usedByTransitSystem
Indicates that something is utilized or operated by a transit or public transportation system.
-
C.
associatedWithTransitSystem
Indicates that an entity has a connection or involvement with a particular transit or transportation system.
-
D.
appliesToTransitStation
Indicates that something (such as a rule, feature, condition, or attribute) is specifically relevant or applicable to a transit station.
-
E.
hasPublicTransitRole
Indicates that an entity holds a specific functional role or responsibility within a public 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddf46948190b8625811725fe41d |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.