Triple
T16045989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castletownbere |
E389219
|
entity |
| Predicate | hasHarbourCharacteristic |
P44134
|
FINISHED |
| Object | sheltered |
—
|
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: sheltered | Statement: [Castletownbere, hasHarbourCharacteristic, sheltered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourCharacteristic Context triple: [Castletownbere, hasHarbourCharacteristic, sheltered]
-
A.
hasHarborFeature
chosen
Indicates that something possesses or includes a specific harbor-related characteristic, structure, or facility.
-
B.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
C.
hasAncestralHarbour
Indicates that an entity has a harbour that historically served as the origin or ancestral port associated with it.
-
D.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
E.
hasPrivateHarbour
Indicates that an entity possesses or is associated with its own exclusive harbour not shared with the general public.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.