Triple
T26946762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guachichil |
E678664
|
entity |
| Predicate | approximateLanguageFamily |
P171017
|
FINISHED |
| Object | Uto-Aztecan 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: Uto-Aztecan languages | Statement: [Guachichil, approximateLanguageFamily, Uto-Aztecan languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateLanguageFamily Context triple: [Guachichil, approximateLanguageFamily, Uto-Aztecan languages]
-
A.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
B.
possiblyRepresentsLanguageFamily
chosen
Indicates that one entity may, but does not certainly, denote or correspond to the language family of the other entity.
-
C.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
D.
languageFamilyOfMajorLanguage
Indicates that one entity is the language family to which the other, a major language, belongs.
-
E.
basedOnLanguageFamily
Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 6:22 a.m.