Triple
T26140163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iona Island (Paterson Inlet) |
E659493
|
entity |
| Predicate | locatedInBayOrInlet |
P109263
|
FINISHED |
| Object | Paterson Inlet / Whaka a Te Wera |
—
|
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: Paterson Inlet / Whaka a Te Wera | Statement: [Iona Island (Paterson Inlet), locatedInBayOrInlet, Paterson Inlet / Whaka a Te Wera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBayOrInlet Context triple: [Iona Island (Paterson Inlet), locatedInBayOrInlet, Paterson Inlet / Whaka a Te Wera]
-
A.
locatedInBayOf
chosen
Indicates that something is situated within or directly on a specific bay.
-
B.
locatedOnWaterbody
Indicates that an entity is situated on or directly adjacent to a specified body of water.
-
C.
partOfHarborOrSound
Indicates that one entity is a component, area, or feature within a harbor or sound.
-
D.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
E.
locatedInHarbourArea
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 26, 2026, 8:19 p.m.