Triple
T2080878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Sound |
E45237
|
entity |
| Predicate | hasWaveExposure |
P14188
|
FINISHED |
| Object | exposed coastal waters |
—
|
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: exposed coastal waters | Statement: [Broad Sound, hasWaveExposure, exposed coastal waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaveExposure Context triple: [Broad Sound, hasWaveExposure, exposed coastal waters]
-
A.
hasWaveClimate
Indicates a relationship where a location or coastal area is characterized by a particular pattern or regime of wave conditions (such as height, period, and direction).
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
-
D.
exposed
chosen
Indicates that one entity has been made visible, revealed, or left unprotected to another entity or to some external influence.
-
E.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.