Triple
T17494652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Nicholson |
E426024
|
entity |
| Predicate | isShelteredHarbour |
P77749
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Port Nicholson, isShelteredHarbour, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShelteredHarbour Context triple: [Port Nicholson, isShelteredHarbour, true]
-
A.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
B.
isShoreEstablishmentOf
Indicates that one entity is a land-based (shore) facility that belongs to, supports, or is administratively part of another maritime or naval organization or unit.
-
C.
locatedInHarbourArea
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
D.
hasNearbyHarbor
Indicates that one location has a harbor situated close to it in geographic proximity.
-
E.
hasHarborProtection
chosen
Indicates that an entity provides or is subject to protective measures for a harbor, such as defense, safety, or sheltering functions.
- 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_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d782688190afb76fa080867315 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.