Triple
T31719576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guruntum people |
E809535
|
entity |
| Predicate | nativeLanguageGroup |
P92545
|
FINISHED |
| Object | Barawa (Zaar) 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: Barawa (Zaar) languages | Statement: [Guruntum people, nativeLanguageGroup, Barawa (Zaar) languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeLanguageGroup Context triple: [Guruntum people, nativeLanguageGroup, Barawa (Zaar) languages]
-
A.
primaryLanguageGroup
Indicates that the related entities share or belong to the same main or dominant language group.
-
B.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
C.
majorLanguageGroupOf
Indicates that one language group is the primary or dominant linguistic classification to which another language or set of languages belongs.
-
D.
nativeLanguageFamilyName
Indicates the name of the language family to which an entity’s native language belongs.
-
E.
languageGroupSpoken
chosen
Indicates that a particular language group is spoken or used for communication by an entity.
- 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_69f6bbbef7a88190b0affdec1d41c1e0 |
completed | May 3, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: April 30, 2026, 11:18 p.m.