Triple
T37519988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnt Green Junction |
E932740
|
entity |
| Predicate | historicalRailwayLine |
P848
|
FINISHED |
| Object | Midland Railway main line |
E45516
|
NE 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: Midland Railway main line | Statement: [Barnt Green Junction, historicalRailwayLine, Midland Railway main line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRailwayLine Context triple: [Barnt Green Junction, historicalRailwayLine, Midland Railway main line]
-
A.
formerRailwayLine
Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
-
B.
railwayLine
chosen
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
C.
railwayLineOpened
Indicates that a railway line began official operation or service on a specified date.
-
D.
isWesternTerminusOfHistoricLine
Indicates that something serves as the western endpoint of a historically significant route, line, or transportation corridor.
-
E.
originalRailway
Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
- F. None of above.
Provenance (4 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01a534a8908190aa888d6be5deb824 |
completed | May 11, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40953f4c2481909c758cc384516100 |
completed | June 28, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_6a01a507c1f081909ff6abc5575db0bb |
completed | May 11, 2026, 9:44 a.m. |
Created at: May 3, 2026, 4:17 p.m.