Triple
T37955772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakwa language |
E946857
|
entity |
| Predicate | countryStatusInSouthSudan |
P204489
|
FINISHED |
| Object | minority 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: minority language | Statement: [Kakwa language, countryStatusInSouthSudan, minority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryStatusInSouthSudan Context triple: [Kakwa language, countryStatusInSouthSudan, minority language]
-
A.
populationRankInSudan
Indicates the relative position of an entity in terms of population size compared to other entities within Sudan.
-
B.
hasLegalStatusInSudan
Indicates that an entity holds a recognized legal status or standing within the jurisdiction of Sudan.
-
C.
languageStatusInSudan
Indicates the recognized or functional status of a language specifically within the context of Sudan.
-
D.
administrativeDivisionOfSudan
Indicates that one entity is an official administrative subdivision or territorial unit within the country of Sudan.
-
E.
primaryLocationInSudan
Indicates that the primary or main location associated with an entity is situated within the country of Sudan.
- F. None of above. chosen
Provenance (4 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:20 p.m.