Triple
T33084361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poqueira Gorge |
E846596
|
entity |
| Predicate | notableVillageCluster |
P165354
|
FINISHED |
| Object | Barranco de Poqueira villages |
—
|
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: Barranco de Poqueira villages | Statement: [Poqueira Gorge, notableVillageCluster, Barranco de Poqueira villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVillageCluster Context triple: [Poqueira Gorge, notableVillageCluster, Barranco de Poqueira villages]
-
A.
hasVillageCluster
chosen
Indicates that one entity contains, is associated with, or is organized into a specific cluster or grouping of villages.
-
B.
isVillageCenterOf
Indicates that a location functions as the central or main hub area of a specified village.
-
C.
notableCommunity
Indicates that an entity is a particularly prominent or significant member of a given community.
-
D.
notablePropertyCluster
Indicates that multiple notable properties are grouped together as a coherent cluster or set associated with an entity.
-
E.
capitalVillage
Indicates that a village serves as the administrative or political capital of a specified region or 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:26 a.m.