Triple
T34236549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolleston railway station |
E878348
|
entity |
| Predicate | regionRailCode |
P71744
|
FINISHED |
| Object | East Midlands route |
—
|
NE NERFINISHED |
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: East Midlands route | Statement: [Rolleston railway station, regionRailCode, East Midlands route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionRailCode Context triple: [Rolleston railway station, regionRailCode, East Midlands route]
-
A.
railroadCodeFor
Indicates that a specific railroad code is assigned to or used to identify a particular railroad entity.
-
B.
railwayCodeType
Indicates the specific classification or type category assigned to a railway code within a railway coding system.
-
C.
networkRailRouteCode
chosen
Indicates that a specific Network Rail route code is assigned to or associated with an entity, identifying the rail route it belongs to or operates on.
-
D.
railwayCompanyCode
Indicates the identifying code assigned to a railway company that operates or manages the related railway entity.
-
E.
railwayRegion
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:56 a.m.