Triple
T37907273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 motorway (via M12) |
E945587
|
entity |
| Predicate | linkedBySpur |
P198897
|
FINISHED |
| Object | M12 motorway |
—
|
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: M12 motorway | Statement: [M1 motorway (via M12), linkedBySpur, M12 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedBySpur Context triple: [M1 motorway (via M12), linkedBySpur, M12 motorway]
-
A.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
B.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
-
C.
linkedByCorridor
Indicates that two locations are directly connected to each other by a corridor.
-
D.
linkedSector
Indicates that one sector is associated or connected to another sector in a meaningful or relevant way.
-
E.
linkedPosition
Indicates that one position is associated or connected to another position in a defined way.
- 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_69f76ef20bb0819088b5b6ceecb0b8fc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
| PDg | Predicate description generation | batch_69ff10956d3881909144f880f92e90c4 |
completed | May 9, 2026, 10:46 a.m. |
Created at: May 3, 2026, 4:20 p.m.