Triple
T29693829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCH |
E751284
|
entity |
| Predicate | appliesToRailLine |
P15901
|
FINISHED |
| Object | Ely–Peterborough line |
—
|
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: Ely–Peterborough line | Statement: [MCH, appliesToRailLine, Ely–Peterborough line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToRailLine Context triple: [MCH, appliesToRailLine, Ely–Peterborough line]
-
A.
appliesToRailwayNetwork
Indicates that something is relevant or specifically applicable to a railway network as a whole.
-
B.
appliesToTransitLine
chosen
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
-
C.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
E.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
- 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_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 28, 2026, 7:18 p.m.