Triple
T16839310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babraham Road |
E409364
|
entity |
| Predicate | isPartOfRouteTowards |
P68000
|
FINISHED |
| Object | A11 corridor |
—
|
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: A11 corridor | Statement: [Babraham Road, isPartOfRouteTowards, A11 corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfRouteTowards Context triple: [Babraham Road, isPartOfRouteTowards, A11 corridor]
-
A.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
B.
isInTravelDirection
Indicates that one entity lies along or matches the direction in which another entity is traveling or moving.
-
C.
isStrategicRouteFor
Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
-
D.
locatedOnRouteTo
chosen
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
E.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34f902c8190a334ba7caa04ce7e |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.