Triple
T15411379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benacre |
E368599
|
entity |
| Predicate | hasCoastalErosion |
P75701
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Benacre, hasCoastalErosion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalErosion Context triple: [Benacre, hasCoastalErosion, true]
-
A.
hasCoastalRisk
Indicates that an entity is exposed to potential hazards or adverse impacts associated with coastal environments, such as flooding, erosion, or storm surge.
-
B.
hasCoastalProtectionConcern
Indicates that an entity has an issue, risk, or consideration related to protecting coastal areas from environmental or human impacts.
-
C.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
D.
hasCoastalCharacteristic
chosen
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
E.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea600b48190a3dbca1a68a2a1cd |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.