Triple
T37489129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 motorway |
E931624
|
entity |
| Predicate | formsPrimaryRoute |
P147208
|
FINISHED |
| Object | Dublin–Sligo corridor |
—
|
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: Dublin–Sligo corridor | Statement: [M4 motorway, formsPrimaryRoute, Dublin–Sligo corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsPrimaryRoute Context triple: [M4 motorway, formsPrimaryRoute, Dublin–Sligo corridor]
-
A.
primaryRouteFrom
Indicates that one entity serves as the main or preferred route originating from another entity.
-
B.
formsKeyRouteTo
Indicates that something serves as a primary or essential pathway or connection leading to another thing.
-
C.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
D.
primaryRouteOf
chosen
Indicates that one route is the main or most important pathway used for reaching or connecting to a particular destination or entity.
-
E.
primaryRoutes
Indicates the main or most important routes that connect or serve between specified locations or entities.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: May 3, 2026, 4:17 p.m.