Triple
T21326287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connah's Quay |
E525764
|
entity |
| Predicate | hasHarbourActivity |
P143725
|
FINISHED |
| Object | shipping |
—
|
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: shipping | Statement: [Connah's Quay, hasHarbourActivity, shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourActivity Context triple: [Connah's Quay, hasHarbourActivity, shipping]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarbourAuthority
Indicates that one entity holds official authority or administrative control over the operations and management of a harbour associated with another entity.
-
C.
hasHarborOpened
Indicates that a harbor has been officially opened and is available for use or operation.
-
D.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
E.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab49aa48819083b3793657903216 |
completed | April 21, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:41 p.m.