Triple
T6130425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M66 motorway |
E136702
|
entity |
| Predicate | northernTerminusConnects |
P69344
|
FINISHED |
| Object | A56 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: A56 road | Statement: [M66 motorway, northernTerminusConnects, A56 road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northernTerminusConnects Context triple: [M66 motorway, northernTerminusConnects, A56 road]
-
A.
northernTerminusRegion
Indicates that a location or route has its northern endpoint or final stopping point within a specified region.
-
B.
northernTerminusMunicipality
Indicates that a municipality serves as the northern endpoint or terminus of a route, line, or similar linear feature.
-
C.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
-
D.
northTerminusType
Indicates the type or nature of the northern endpoint or terminus of a route, line, or similar linear feature.
-
E.
northernTerminusState
Indicates that a location or route has its northern endpoint or terminus within the specified state.
- F. None of above. chosen
Provenance (4 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c4de9c48190b98f67a6251ec1df |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:15 p.m.