Triple
T36782468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conibo |
E908810
|
entity |
| Predicate | isPartOfBroaderCategory |
P8622
|
FINISHED |
| Object | Indigenous peoples of the Amazon basin |
—
|
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: Indigenous peoples of the Amazon basin | Statement: [Conibo, isPartOfBroaderCategory, Indigenous peoples of the Amazon basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfBroaderCategory Context triple: [Conibo, isPartOfBroaderCategory, Indigenous peoples of the Amazon basin]
-
A.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
-
B.
hasCategoryWithin
Indicates that one category is contained within or is a subcategory of another category.
-
C.
isOneOfMajorCategories
Indicates that an entity belongs to a specified set of primary or top-level categories within a classification.
-
D.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
E.
hasParentCategory
chosen
Indicates that an entity belongs to or is organized under a broader, more general category.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 3, 2026, 4:12 p.m.