Triple
T25391019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tournan |
E636165
|
entity |
| Predicate | commuterRailFunction |
P95592
|
FINISHED |
| Object | terminus station |
—
|
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: terminus station | Statement: [Tournan, commuterRailFunction, terminus station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commuterRailFunction Context triple: [Tournan, commuterRailFunction, terminus station]
-
A.
commuterRailMode
Indicates that the relationship involves travel or transportation specifically by commuter rail as the mode of transit between the related entities.
-
B.
operatesCommuterRailServices
Indicates that an entity runs and manages commuter rail transportation services for passengers.
-
C.
servesCommuterRailLine
chosen
Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
-
D.
operatesCommuterServiceBetween
Indicates that an entity runs a commuter transportation service connecting two specified locations.
-
E.
hasCommuterServices
Indicates that a location or facility provides transportation services specifically intended for regular commuters, such as daily or frequent travelers between home and work or school.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5657015648190bee3b56dceac3b10 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:49 p.m.