Triple
T20152469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debourg |
E491466
|
entity |
| Predicate | isEndStationOf |
P34947
|
FINISHED |
| Object | T1 line southbound direction |
—
|
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: T1 line southbound direction | Statement: [Debourg, isEndStationOf, T1 line southbound direction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndStationOf Context triple: [Debourg, isEndStationOf, T1 line southbound direction]
-
A.
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.
-
B.
isPassengerStationFor
Indicates that a station serves as a boarding and alighting point for passengers on a particular transportation line or service.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
hasEndpointStation
chosen
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
E.
startingStation
Indicates the station or location where a journey, route, or trip begins.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667dda9b4819097ff66bb2b50fc21 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.