Triple
T33150057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosslare–Cherbourg ferry route |
E848410
|
entity |
| Predicate | linksToRoadNetwork |
P176401
|
FINISHED |
| Object | Irish road network |
—
|
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: Irish road network | Statement: [Rosslare–Cherbourg ferry route, linksToRoadNetwork, Irish road network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linksToRoadNetwork Context triple: [Rosslare–Cherbourg ferry route, linksToRoadNetwork, Irish road network]
-
A.
connectsRoadNetwork
Indicates that one entity is linked to another as part of the same road network, enabling continuous vehicular or transport connectivity between them.
-
B.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
C.
streetNetwork
Indicates the layout and connectivity relationships among streets within a geographic area, including how roads intersect, link, and form a navigable network.
-
D.
roadNetworkPartOf
Indicates that one road network segment or component is a constituent part of a larger road network.
-
E.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6e029f0f88190b1f88d82a4a2cabd |
completed | May 3, 2026, 5:42 a.m. |
Created at: May 1, 2026, 1:28 a.m.