Triple
T36251879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indigenous peoples of the Amazon Basin |
E891823
|
entity |
| Predicate | speakLanguageFamily |
P64840
|
FINISHED |
| Object | Tupian languages |
—
|
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: Tupian languages | Statement: [Indigenous peoples of the Amazon Basin, speakLanguageFamily, Tupian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakLanguageFamily Context triple: [Indigenous peoples of the Amazon Basin, speakLanguageFamily, Tupian languages]
-
A.
usesLanguageFamily
chosen
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
B.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
C.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
D.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
E.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fab9908190aaecb5e3c6dd1f9f |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.