Triple
T16470792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5MT |
E400052
|
entity |
| Predicate | railwayRegionContext |
P15232
|
FINISHED |
| Object | former LMS routes |
—
|
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: former LMS routes | Statement: [5MT, railwayRegionContext, former LMS routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayRegionContext Context triple: [5MT, railwayRegionContext, former LMS routes]
-
A.
railwayRegion
chosen
Indicates a relationship where a railway or rail network is associated with, located in, or administered within a particular geographic region.
-
B.
railwayDivision
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
-
C.
reopenedRailwayContext
Indicates that a railway line, previously closed or inactive, has been put back into operation within a specified context or timeframe.
-
D.
railwayGaugeContext
Indicates the specific track gauge standard or measurement that applies to, or is used in, a given railway-related context.
-
E.
railPortalLocation
Indicates the geographic location or position of a rail portal (such as a tunnel or access point) relative to other referenced entities.
- 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_69d87f2dac988190b74d6e185fa88ba4 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32dd0d2fc81909b68b5afb00f192f |
completed | April 18, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69e22706b0588190a48a951c5211a617 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:11 a.m.