Triple
T26464555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U’wa |
E665724
|
entity |
| Predicate | hasCollectiveTerritory |
P158735
|
FINISHED |
| Object | Resguardo Unido U’wa |
—
|
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: Resguardo Unido U’wa | Statement: [U’wa, hasCollectiveTerritory, Resguardo Unido U’wa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveTerritory Context triple: [U’wa, hasCollectiveTerritory, Resguardo Unido U’wa]
-
A.
collectiveTerritories
chosen
Indicates that multiple entities share or jointly possess a set of territories as a collective whole.
-
B.
hasTerritorialInterestIn
Indicates that an entity claims, seeks, or maintains control, influence, or rights over a specific geographic area or territory.
-
C.
hasLargeTerritory
Indicates that an entity occupies or controls a geographically extensive area relative to typical or comparable entities.
-
D.
coRuledTerritoryWith
Indicates that two or more rulers shared authority over the same territory during an overlapping period of rule.
-
E.
affectsTerritoryOf
Indicates that one entity causes changes to, or has an impact on, the territorial domain or jurisdiction of another 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 27, 2026, 12:15 a.m.