Triple
T28003979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Watford–Luton rivalry |
E707222
|
entity |
| Predicate | sharedTransportLink |
P59961
|
FINISHED |
| Object | M1 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: M1 motorway | Statement: [Watford–Luton rivalry, sharedTransportLink, M1 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharedTransportLink Context triple: [Watford–Luton rivalry, sharedTransportLink, M1 motorway]
-
A.
transportLinkType
Indicates the specific kind of transportation connection or route that exists between two locations or transport nodes.
-
B.
isTransportationLinkBetween
Indicates that there exists a transportation connection (such as a road, rail, air, or sea route) linking the two entities.
-
C.
servesTransportLinks
Indicates that one entity provides or supports transportation connections or routes for another entity or area.
-
D.
shareTransportInfrastructure
chosen
Indicates that multiple entities make joint use of the same transport infrastructure facilities or systems.
-
E.
transportLinkVisible
Indicates that a transportation connection between locations is currently observable or accessible within the given context.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 27, 2026, 7:59 p.m.