Triple
T33042747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 motorway near Chieveley |
E845511
|
entity |
| Predicate | isKeyNodeOnRoute |
P6309
|
FINISHED |
| Object | London–Bristol–South Wales corridor |
—
|
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: London–Bristol–South Wales corridor | Statement: [M4 motorway near Chieveley, isKeyNodeOnRoute, London–Bristol–South Wales corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyNodeOnRoute Context triple: [M4 motorway near Chieveley, isKeyNodeOnRoute, London–Bristol–South Wales corridor]
-
A.
isKeyNodeIn
Indicates that a node serves as a primary or critical element within a specified structure, system, or context.
-
B.
isKeyRoute
Indicates that a route plays a primary or strategically important role within a network or system.
-
C.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
-
D.
isPartOfRoute
chosen
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
E.
isKeyRoadLinkBetween
Indicates that a road segment functions as a primary connecting link between two specific locations or road network elements.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:24 a.m.