Triple
T25319178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cávado |
E634830
|
entity |
| Predicate | containsCoastalMunicipality |
P41457
|
FINISHED |
| Object | Esposende |
—
|
NE NERFINISHED |
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: Esposende | Statement: [Cávado, containsCoastalMunicipality, Esposende]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsCoastalMunicipality Context triple: [Cávado, containsCoastalMunicipality, Esposende]
-
A.
hasCoastalMunicipalities
chosen
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
B.
hasCoastalCommunes
Indicates that an administrative region possesses one or more communes that are located on or directly adjacent to a sea or ocean coastline.
-
C.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
D.
hasCoastalFrazione
Indicates that an administrative area has at least one subordinate locality (frazione) that is situated on the coast.
-
E.
isCoastalCityLocality
Indicates that a city or locality is situated on or very near a sea or ocean coastline.
- 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 21, 2026, 1:28 p.m.