Triple
T29693811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCH |
E751284
|
entity |
| Predicate | locatedInRailwayRegion |
P15232
|
FINISHED |
| Object | East of England |
—
|
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 of England | Statement: [MCH, locatedInRailwayRegion, East of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInRailwayRegion Context triple: [MCH, locatedInRailwayRegion, East of England]
-
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.
isRegionalRailwayHub
Indicates that a location functions as a central node in a regional railway network, where multiple rail lines converge or are coordinated.
-
C.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
D.
hasRailwayZone
Indicates that a location or railway entity falls under the jurisdiction or coverage area of a specific railway zone.
-
E.
isOnRailway
Indicates that one entity is positioned on, aligned with, or traveling along a railway track or railway system in relation to another entity.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: April 28, 2026, 7:18 p.m.