Triple
T37343163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankuamo |
E927098
|
entity |
| Predicate | legalCategoryInColombia |
P76736
|
FINISHED |
| Object | Indigenous community |
—
|
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: Indigenous community | Statement: [Kankuamo, legalCategoryInColombia, Indigenous community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCategoryInColombia Context triple: [Kankuamo, legalCategoryInColombia, Indigenous community]
-
A.
juridicalCategory
chosen
Indicates the legal classification or status under which an entity or relationship is formally recognized in a juridical system.
-
B.
legalCategoryInIndia
Indicates that an entity belongs to a specific legally defined category or classification under Indian law.
-
C.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
-
D.
legalFeature
Indicates that something possesses a specific legal characteristic, status, or attribute relevant to laws or regulations.
-
E.
legalConcept
Indicates a relationship where something is classified or treated as a concept defined and governed by law or legal theory.
- 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff59a00a881909b35b799654b3c45 |
completed | May 10, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69fff4d0a2e081909c972189b33d0128 |
completed | May 10, 2026, 3 a.m. |
Created at: May 3, 2026, 4:16 p.m.