Triple
T12040017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bemba language |
E286634
|
entity |
| Predicate | statusInZambia |
P102895
|
FINISHED |
| Object | major lingua franca |
—
|
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: major lingua franca | Statement: [Bemba language, statusInZambia, major lingua franca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInZambia Context triple: [Bemba language, statusInZambia, major lingua franca]
-
A.
statusInZimbabwe
Indicates the legal, social, or official standing or condition that an entity holds within the context of Zimbabwe.
-
B.
statusInBotswana
Indicates that an entity has a particular legal, social, or operational status specifically within the context of Botswana.
-
C.
countryStatusInZimbabwe
Indicates the legal or diplomatic status that an entity holds within or in relation to Zimbabwe.
-
D.
statusInNamibia
Indicates that an entity holds a particular legal, social, or operational status within the context or jurisdiction of Namibia.
-
E.
statusInMali
Indicates the legal, social, or official condition or standing that an entity holds within the context of Mali.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bac9e08190aa1a99c835f29542 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d91006e14081909838412df082f794 |
completed | April 10, 2026, 2:58 p.m. |
Created at: April 8, 2026, 9:47 p.m.