Triple
T27472203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keene station |
E693350
|
entity |
| Predicate | servedAsStopOn |
P160597
|
FINISHED |
| Object | major rail line in the region |
—
|
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: major rail line in the region | Statement: [Keene station, servedAsStopOn, major rail line in the region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsStopOn Context triple: [Keene station, servedAsStopOn, major rail line in the region]
-
A.
servesStop
Indicates that a transportation route or service includes a particular stop as one of its locations where it picks up or drops off passengers.
-
B.
stopsAtStation
Indicates that a vehicle or service halts at a particular station as part of its route or schedule.
-
C.
railNetworkStopOn
chosen
Indicates that a rail stop or station is located on and served by a particular rail network.
-
D.
hasStopNear
Indicates that one entity has a stop or stopping point located in close proximity to another entity.
-
E.
isPassengerStop
Indicates that a location serves as a designated place where passengers may board or alight from a vehicle or transport service.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 27, 2026, 12:54 p.m.