Triple
T32195258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N31 road |
E822386
|
entity |
| Predicate | connectsPortToNetwork |
P197958
|
FINISHED |
| Object | Dún Laoghaire Harbour |
—
|
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: Dún Laoghaire Harbour | Statement: [N31 road, connectsPortToNetwork, Dún Laoghaire Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsPortToNetwork Context triple: [N31 road, connectsPortToNetwork, Dún Laoghaire Harbour]
-
A.
connectsPortToHinterland
Indicates that a port serves as a transport or logistical link to its surrounding inland (hinterland) region.
-
B.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
-
C.
connectsPortRegion
Indicates that one entity serves as a linkage or interface between a specific port and a defined region.
-
D.
belongsToPortNetwork
Indicates that something is a member of, or associated with, a specific port network.
-
E.
portConnections
Indicates that there exists a connection or linkage between two ports or interfaces.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_69febce420b081908e1c052751a22b1f |
completed | May 9, 2026, 4:49 a.m. |
Created at: May 1, 2026, 12:35 a.m.