Triple
T32110502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hole in the Rock (Motukōkako) |
E820104
|
entity |
| Predicate | isOffCoastOf |
P15643
|
FINISHED |
| Object | Cape Brett |
—
|
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: Cape Brett | Statement: [Hole in the Rock (Motukōkako), isOffCoastOf, Cape Brett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOffCoastOf Context triple: [Hole in the Rock (Motukōkako), isOffCoastOf, Cape Brett]
-
A.
isCoastalDestinationFor
Indicates that a place serves as a seaside or ocean-adjacent travel destination for a particular person, group, or market.
-
B.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
C.
isCoastalTo
Indicates that one place is located along or directly borders the coastline of another body of water or coastal region.
-
D.
coastOff
chosen
Indicates that one entity is located just off the coast of another, typically in nearby offshore waters rather than directly on the shoreline.
-
E.
isSeawardOf
Indicates that one location lies closer to or toward the sea relative to another location.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b69f49d881909de19dec9c5459c5 |
completed | May 3, 2026, 2:44 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:27 a.m.