Triple
T21476732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandhaven |
E529880
|
entity |
| Predicate | coastalUse |
P20797
|
FINISHED |
| Object | small-scale commercial fishing |
—
|
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: small-scale commercial fishing | Statement: [Sandhaven, coastalUse, small-scale commercial fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalUse Context triple: [Sandhaven, coastalUse, small-scale commercial fishing]
-
A.
hasCoastalFunction
Indicates that something serves a role, purpose, or activity specifically related to the coast or coastal areas.
-
B.
coastalInteraction
Indicates an interaction or relationship occurring between entities and a coastal environment, such as along shorelines or near the sea.
-
C.
hasShorelineUse
chosen
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
D.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
E.
hasCoastalRecreation
Indicates that an entity provides, supports, or is associated with recreational activities occurring along a coast or shoreline.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea187a3c8190b3f33bd760dc1f54 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:20 p.m.