Triple
T30441087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M6 Junction 1 |
E774444
|
entity |
| Predicate | providesAccessTowards |
P42312
|
FINISHED |
| Object | Catthorpe Interchange |
—
|
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: Catthorpe Interchange | Statement: [M6 Junction 1, providesAccessTowards, Catthorpe Interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesAccessTowards Context triple: [M6 Junction 1, providesAccessTowards, Catthorpe Interchange]
-
A.
accessProvides
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
accessDirection
chosen
Indicates the direction or orientation from which access to something is obtained or permitted.
-
D.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
E.
improvesAccessToward
Indicates that one entity enhances or facilitates the ability of another entity to reach, use, or benefit from a resource, service, or opportunity.
- 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_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 29, 2026, 8:08 p.m.