Triple
T18327222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidestrand |
E439041
|
entity |
| Predicate | hasCoastalProtectionIssues |
P97587
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sidestrand, hasCoastalProtectionIssues, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalProtectionIssues Context triple: [Sidestrand, hasCoastalProtectionIssues, yes]
-
A.
hasCoastalProtectionConcern
chosen
Indicates that an entity has an issue, risk, or consideration related to protecting coastal areas from environmental or human impacts.
-
B.
hasCoastalRisk
Indicates that an entity is exposed to potential hazards or adverse impacts associated with coastal environments, such as flooding, erosion, or storm surge.
-
C.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
D.
coastalProtection
Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
-
E.
isCoastalCommunity
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aab3e7c81909b1c0a688707dfd6 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.