Triple
T33214557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadden Sea coastal clay area |
E850251
|
entity |
| Predicate | hasBoundaryElement |
P6131
|
FINISHED |
| Object | sea dike |
—
|
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 dike | Statement: [Wadden Sea coastal clay area, hasBoundaryElement, sea dike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoundaryElement Context triple: [Wadden Sea coastal clay area, hasBoundaryElement, sea dike]
-
A.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
-
B.
hasBoundaryType
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
C.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
D.
hasBoundaryFeature
chosen
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
E.
hasBoundaryIncludes
Indicates that the spatial or conceptual boundary of one entity encompasses or contains the boundary of another entity.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 1, 2026, 1:30 a.m.