Triple
T31951220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapuche communities of Wallmapu |
E815782
|
entity |
| Predicate | hasTerritoryConcept |
P21614
|
FINISHED |
| Object | ancestral territory |
—
|
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: ancestral territory | Statement: [Mapuche communities of Wallmapu, hasTerritoryConcept, ancestral territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerritoryConcept Context triple: [Mapuche communities of Wallmapu, hasTerritoryConcept, ancestral territory]
-
A.
hasDefinedTerritory
Indicates that an entity possesses a specific, delimited geographic or conceptual area over which it has recognized control or jurisdiction.
-
B.
hasTerritorialAssociation
chosen
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
C.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
D.
hasComponentTerritory
Indicates that one territory is a constituent or subordinate part of a larger, encompassing territory.
-
E.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 12:07 a.m.