Triple
T30416186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribeira de Seixe estuary |
E773762
|
entity |
| Predicate | municipalityOnSouthBank |
P176336
|
FINISHED |
| Object | Aljezur |
—
|
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: Aljezur | Statement: [Ribeira de Seixe estuary, municipalityOnSouthBank, Aljezur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: municipalityOnSouthBank Context triple: [Ribeira de Seixe estuary, municipalityOnSouthBank, Aljezur]
-
A.
stateOnSouthBank
Indicates that one entity (typically a state or region) is located on the southern bank of another geographic feature, such as a river or body of water.
-
B.
municipalityOnNorthBank
Indicates that a municipality is located on the northern bank of a river or similar water body.
-
C.
municipalityOnEastBank
Indicates that a municipality is located on the eastern bank of a river or similar water body.
-
D.
countryOnSouthBank
Indicates that a country is located on the southern bank of a specified river or water body.
-
E.
hasJurisdictionOnSouthBank
Indicates that an authority or entity holds legal or administrative control over the south bank of a specified area or feature.
- F. None of above. chosen
Provenance (4 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 29, 2026, 8:05 p.m.