Triple
T3594555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol to Exeter Line |
E76104
|
entity |
| Predicate | linkToOtherMainLine |
P35426
|
FINISHED |
| Object | CrossCountry network at Bristol |
—
|
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: CrossCountry network at Bristol | Statement: [Bristol to Exeter Line, linkToOtherMainLine, CrossCountry network at Bristol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkToOtherMainLine Context triple: [Bristol to Exeter Line, linkToOtherMainLine, CrossCountry network at Bristol]
-
A.
connectsToMainLineAt
chosen
Indicates that one entity is linked or joined to a primary or central line at a specific point.
-
B.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
C.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
-
D.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
-
E.
associatedLine
Indicates that one entity is linked or connected to a particular line (such as a line item, line of text, or line in a structure) with which it is contextually or functionally related.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15d3e308190b8352ef1f054f9c3 |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.