Triple
T34176957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midgham railway station |
E876698
|
entity |
| Predicate | trainServices |
P21523
|
FINISHED |
| Object | local stopping services |
—
|
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: local stopping services | Statement: [Midgham railway station, trainServices, local stopping services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainServices Context triple: [Midgham railway station, trainServices, local stopping services]
-
A.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
B.
railServiceType
chosen
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
C.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
D.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
-
E.
railAuthority
Indicates that an entity has official regulatory or operational control over railway systems or services.
- 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_69f349ad97ac8190bf1f17417c970e64 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 1:54 a.m.