Triple
T32586950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea ferry network |
E832946
|
entity |
| Predicate | hasNodePort |
P114090
|
FINISHED |
| Object | Port of Harwich |
—
|
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: Port of Harwich | Statement: [North Sea ferry network, hasNodePort, Port of Harwich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNodePort Context triple: [North Sea ferry network, hasNodePort, Port of Harwich]
-
A.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
-
B.
hasNode
chosen
Indicates that one entity contains, includes, or is associated with a particular node as part of its structure or composition.
-
C.
hasUserPort
Indicates that an entity is associated with, exposes, or is accessible through a specific user-facing port or interface.
-
D.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
-
E.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a013a251b4081908b43d85dd95586c5 |
completed | May 11, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a0137e4ea988190812173a5ff044098 |
completed | May 11, 2026, 1:59 a.m. |
Created at: May 1, 2026, 1:04 a.m.