Triple
T15810133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musi Nadi |
E383323
|
entity |
| Predicate | localLanguageRegion |
P29819
|
FINISHED |
| Object | Musi language |
—
|
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: Musi language | Statement: [Musi Nadi, localLanguageRegion, Musi language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localLanguageRegion Context triple: [Musi Nadi, localLanguageRegion, Musi language]
-
A.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
B.
localLanguageName
Indicates the name of a language as it is written or referred to in its own local or native form.
-
C.
languageFamilyRegion
Indicates the geographic region or area in which a language family is predominantly found or historically associated.
-
D.
alsoInLanguageRegion
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
E.
languageArea
chosen
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52aae14819091de08630e7e1d1a |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.