Triple
T24336290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuracaré |
E613390
|
entity |
| Predicate | hasCollectiveLandClaims |
P118181
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Yuracaré, hasCollectiveLandClaims, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectiveLandClaims Context triple: [Yuracaré, hasCollectiveLandClaims, true]
-
A.
hasIndigenousRightsClaims
chosen
Indicates that an entity asserts or is recognized as having legal or customary rights claims based on its status as an Indigenous people or community.
-
B.
hasLandClaimAgreement
Indicates that there exists a formal agreement granting or recognizing a party’s rights or claims to a specific piece of land.
-
C.
hasCollectiveRightClaim
Indicates that a group or collective entity asserts or holds a right or entitlement on behalf of its members.
-
D.
hasHistoricLandGrants
Indicates that an entity has been granted land through one or more historically significant official land grants.
-
E.
historicalSovereigntyClaim
Indicates a relationship where an entity asserts that it held sovereign authority over another entity or territory at some point in the past.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f5346881909ca93b7ceef543ed |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:57 a.m.