Triple
T31719573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guruntum people |
E809535
|
entity |
| Predicate | nativeLanguageFamily |
P71895
|
FINISHED |
| Object | Afroasiatic 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: Afroasiatic languages | Statement: [Guruntum people, nativeLanguageFamily, Afroasiatic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeLanguageFamily Context triple: [Guruntum people, nativeLanguageFamily, Afroasiatic languages]
-
A.
nativeLanguageFamilyName
Indicates the name of the language family to which an entity’s native language belongs.
-
B.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
C.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
-
D.
languageFamilyUsedFor
Indicates that a particular language family is employed or utilized for a specific purpose, context, or function.
-
E.
primaryLocalLanguageFamily
chosen
Indicates the main linguistic family to which the predominant local language of an 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:18 p.m.