Triple
T2444586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broad Channel |
E53359
|
entity |
| Predicate | coastalRisk |
P35656
|
FINISHED |
| Object | flood-prone area |
—
|
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: flood-prone area | Statement: [Broad Channel, coastalRisk, flood-prone area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalRisk Context triple: [Broad Channel, coastalRisk, flood-prone area]
-
A.
isCoastalCommunity
Indicates that a community is located along a coast or shoreline and is directly associated with a nearby sea or ocean.
-
B.
hasTsunamiRisk
Indicates that the subject is exposed to or associated with a potential risk of tsunamis.
-
C.
hasCoastalEnvironment
chosen
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
D.
coastalCluster
Indicates a grouping of entities that are located near or along the same coastal area or shoreline.
-
E.
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).
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcabf477081908512df63ac1a6414 |
completed | March 7, 2026, 6:50 a.m. |
| PD | Predicate disambiguation | batch_69abc5ad8e588190b97c4cd7cf575043 |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.