Triple
T8910426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A249 |
E212167
|
entity |
| Predicate | formsTransportLinkBetween |
P70574
|
FINISHED |
| Object | M2 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: M2 motorway | Statement: [A249, formsTransportLinkBetween, M2 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsTransportLinkBetween Context triple: [A249, formsTransportLinkBetween, M2 motorway]
-
A.
formsTransportCorridorBetween
chosen
Indicates that something creates or constitutes a transportation link or route connecting two locations or entities.
-
B.
formsPrimaryLinkBetween
Indicates that one entity serves as the main or most important connection or linkage between two other entities.
-
C.
transportConnectionTo
Indicates a relationship where one entity provides or participates in a means of transportation that connects or leads to another entity.
-
D.
transportInterface
Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
-
E.
transportFrom
Indicates that something or someone is moved or carried away starting from a specified origin location.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65227d008190b13ba162d0b3c9d1 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.