Triple
T27667995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M621 motorway |
E697280
|
entity |
| Predicate | hasConnectingLinksNear |
P134094
|
FINISHED |
| Object | Leeds |
—
|
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: Leeds | Statement: [M621 motorway, hasConnectingLinksNear, Leeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectingLinksNear Context triple: [M621 motorway, hasConnectingLinksNear, Leeds]
-
A.
hasBorderConnectionPotential
Indicates that two regions or entities are positioned such that they could feasibly share a border or direct boundary under certain conditions.
-
B.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
C.
hasNotableConnectionTo
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
connectsAreaNear
chosen
Indicates that one entity serves as a link or passage between areas that are geographically close to each other.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: April 27, 2026, 2:39 p.m.