Triple
T30416184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribeira de Seixe estuary |
E773762
|
entity |
| Predicate | regionBoundaryBetween |
P39423
|
FINISHED |
| Object | Alentejo and Algarve |
—
|
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: Alentejo and Algarve | Statement: [Ribeira de Seixe estuary, regionBoundaryBetween, Alentejo and Algarve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionBoundaryBetween Context triple: [Ribeira de Seixe estuary, regionBoundaryBetween, Alentejo and Algarve]
-
A.
stateBoundaryBetween
Indicates a boundary line that separates or lies between two states.
-
B.
boundaryBetween
chosen
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
D.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
E.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: April 29, 2026, 8:05 p.m.