Triple
T20765107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omotic |
E511073
|
entity |
| Predicate | classificationWithinAfroasiatic |
P33198
|
FINISHED |
| Object | debated |
—
|
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: debated | Statement: [Omotic, classificationWithinAfroasiatic, debated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationWithinAfroasiatic Context triple: [Omotic, classificationWithinAfroasiatic, debated]
-
A.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
-
B.
basedOnLanguageFamily
Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
-
C.
glottoCategory
chosen
Indicates the linguistic classification or type (such as language family, subgroup, or category) to which a language or dialect is assigned.
-
D.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
E.
isNotIndoEuropean
Indicates that an entity’s language or linguistic affiliation does not belong to the Indo-European 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24bde0c8190b46986b89bf2e037 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:36 p.m.