Triple
T2936721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Beveland |
E79285
|
entity |
| Predicate | hasCoastalProtection |
P41538
|
FINISHED |
| Object | sea dikes |
—
|
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: sea dikes | Statement: [South Beveland, hasCoastalProtection, sea dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalProtection Context triple: [South Beveland, hasCoastalProtection, sea dikes]
-
A.
coastalProtection
chosen
Indicates measures or actions taken to preserve, defend, or stabilize coastal areas against erosion, flooding, or other marine-related impacts.
-
B.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
C.
hasCoastlineDesignation
Indicates that a geographic area’s coastline has been assigned a specific official classification or status.
-
D.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983df5e08190939cd8acf8ad5b55 |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad96088fb481909976b436c2b729d9 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.