Triple
T35982783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaak’awü |
E1040618
|
entity |
| Predicate | associatedLanguageSubfamily |
P207123
|
FINISHED |
| Object | Zoquean languages |
E1044673
|
NE 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: Zoquean languages | Statement: [Yaak’awü, associatedLanguageSubfamily, Zoquean languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedLanguageSubfamily Context triple: [Yaak’awü, associatedLanguageSubfamily, Zoquean languages]
-
A.
usesLanguageSubfamily
Indicates that one entity communicates or operates using a language that belongs to a specified language subfamily.
-
B.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
C.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
D.
influencedLanguageFamily
Indicates that one language family has had a significant impact on the development, structure, or usage of another language family.
-
E.
coversLanguageFamily
Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
- F. None of above. chosen
Provenance (5 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39c3dd03d88190bf8076dd53b21f16 |
completed | June 22, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.