Triple
T21403274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eysturoy Tunnel |
E527964
|
entity |
| Predicate | hasRoundabout |
P143832
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Eysturoy Tunnel, hasRoundabout, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoundabout Context triple: [Eysturoy Tunnel, hasRoundabout, yes]
-
A.
hasRingRoadRole
Indicates that an entity has a specific functional role or responsibility in relation to a ring road.
-
B.
hasRingRoadType
Indicates that an entity is associated with a specific type or classification of ring road.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
hasTrafficIsland
Indicates the presence of a traffic island separating or organizing lanes or directions of vehicular movement within a roadway.
-
E.
isOnCircularRoute
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
- F. None of above. chosen
Provenance (4 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b171f3448190add844a426b0a606 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:27 p.m.