Triple
T2261183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyckman Street (A line) |
E50041
|
entity |
| Predicate | isExpressStation |
P26424
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Dyckman Street (A line), isExpressStation, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isExpressStation Context triple: [Dyckman Street (A line), isExpressStation, no]
-
A.
isMajorStationOn
Indicates that a station serves as a primary or significant stop on a particular route or line.
-
B.
hasExpressTracks
chosen
Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
-
C.
hasEndpointStation
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
D.
canExpress
Indicates that an entity has the ability or capacity to convey, articulate, or communicate something (such as an idea, emotion, or property).
-
E.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc2ea65288190bc8644a07a11dfa9 |
completed | March 7, 2026, 6:17 a.m. |
| PD | Predicate disambiguation | batch_69abbdb592588190ac1ef5e8c54575b1 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.