Triple
T35088965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M50 motorway (Ireland) |
E1012658
|
entity |
| Predicate | busiestMotorwayIn |
P139729
|
FINISHED |
| Object | Ireland |
—
|
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: Ireland | Statement: [M50 motorway (Ireland), busiestMotorwayIn, Ireland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busiestMotorwayIn Context triple: [M50 motorway (Ireland), busiestMotorwayIn, Ireland]
-
A.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
-
B.
isMotorwayIn
chosen
Indicates that a motorway is located within or passes through a specified geographic area or administrative region.
-
C.
expressway
Indicates that one location is connected to another by a high-speed, limited-access roadway designed for fast vehicular travel.
-
D.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service entity.
-
E.
nearestMotorway
Indicates that one entity is the motorway that is geographically closest to the other entity.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.