Triple
T28179915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luchazi language |
E715996
|
entity |
| Predicate | primaryStatusInAngola |
P49093
|
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: [Luchazi language, primaryStatusInAngola, minority language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStatusInAngola Context triple: [Luchazi language, primaryStatusInAngola, minority language]
-
A.
statusInAngola
chosen
Indicates the legal, social, or operational standing or condition that something or someone has within the context of Angola.
-
B.
areaRankInAngola
Indicates the relative position of an entity in a ranking ordered by its area size within Angola.
-
C.
populationRankInAngola
Indicates the relative position of an entity in terms of population size compared to other entities within Angola.
-
D.
primaryStatusInUganda
Indicates the primary legal, social, or operational status an entity holds specifically within the context of Uganda.
-
E.
primaryStatusInDRC
Indicates the main or most significant status an entity holds within the context of the DRC (Democratic Republic of the Congo).
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: April 27, 2026, 10:18 p.m.