Triple
T38147504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arhuaco |
E952657
|
entity |
| Predicate | rightsStruggle |
P3839
|
FINISHED |
| Object | defense of territorial autonomy |
—
|
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: defense of territorial autonomy | Statement: [Arhuaco, rightsStruggle, defense of territorial autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsStruggle Context triple: [Arhuaco, rightsStruggle, defense of territorial autonomy]
-
A.
struggleFor
chosen
Indicates a relationship where one entity exerts effort or engages in conflict in order to obtain, achieve, or defend another entity or goal.
-
B.
meansOfStruggle
Indicates the method, tactic, or form of action used by an entity in carrying out a struggle or conflict.
-
C.
rights
Indicates that an entity possesses entitlements, permissions, or legal/moral claims in relation to another entity or context.
-
D.
rightsCategory
Indicates the classification or type of rights associated with an entity or relationship.
-
E.
rightsMotivation
Indicates a relationship where an action or stance is motivated by concerns about rights, such as protecting, asserting, or promoting legal or moral entitlements.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:21 p.m.