Triple
T32506770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santoña |
E830818
|
entity |
| Predicate | hasMarshland |
P24156
|
FINISHED |
| Object | Santoña estuary |
—
|
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: Santoña estuary | Statement: [Santoña, hasMarshland, Santoña estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarshland Context triple: [Santoña, hasMarshland, Santoña estuary]
-
A.
containsWetland
chosen
Indicates that one area or region includes within its boundaries a wetland ecosystem.
-
B.
hasWetlandsAtMouth
Indicates that a watercourse or water body has wetlands located at or surrounding its mouth where it meets another body of water.
-
C.
hasNearbyWetlandRegion
Indicates that a given location or area is situated close to, or in the vicinity of, a wetland region.
-
D.
hasRiparianZone
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
-
E.
hasRiparianVegetation
Indicates that an area or feature is associated with, bordered by, or contains vegetation growing along the banks of a river, stream, or other watercourse.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a009d623f6c8190b702e2892c52fbb2 |
completed | May 10, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_6a009a3050d48190b64567f28e6ea463 |
completed | May 10, 2026, 2:46 p.m. |
Created at: May 1, 2026, 1 a.m.