Triple
T30441094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M6 Junction 1 |
E774444
|
entity |
| Predicate | connectsRouteType |
P1374
|
FINISHED |
| Object | motorway to primary A-road |
—
|
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: motorway to primary A-road | Statement: [M6 Junction 1, connectsRouteType, motorway to primary A-road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsRouteType Context triple: [M6 Junction 1, connectsRouteType, motorway to primary A-road]
-
A.
connectsDestinationType
Indicates that one entity serves as a connection or link specifically to a destination of a given type.
-
B.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
-
C.
connectedRoute
Indicates that there is a direct or logically continuous path linking two locations or segments within a network.
-
D.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69f22493ef9c8190ae8c2afcb7f994c8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: April 29, 2026, 8:08 p.m.