Triple
T38296807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EG |
E1032109
|
entity |
| Predicate | hasNationalLanguageFamily |
P35817
|
FINISHED |
| Object | Afro-Asiatic |
—
|
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: Afro-Asiatic | Statement: [EG, hasNationalLanguageFamily, Afro-Asiatic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalLanguageFamily Context triple: [EG, hasNationalLanguageFamily, Afro-Asiatic]
-
A.
hasPrimaryVernacularLanguageFamily
Indicates that an entity’s main vernacular language belongs to a specified language family.
-
B.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
C.
areOfficialLanguageFamilyOf
chosen
Indicates that one or more language families hold official status within, or are formally recognized as official for, a particular entity (such as a country or region).
-
D.
usesLanguageFamily
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
E.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 3, 2026, 4:30 p.m.