Triple
T33778619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Okiek language |
E865589
|
entity |
| Predicate | statusInTanzania |
P199151
|
FINISHED |
| Object | endangered |
—
|
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: endangered | Statement: [Okiek language, statusInTanzania, endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInTanzania Context triple: [Okiek language, statusInTanzania, endangered]
-
A.
statusInKenya
Indicates the legal, social, or official standing or condition that an entity holds specifically within the context of Kenya.
-
B.
statusInMozambique
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Mozambique.
-
C.
regionWithinTanzania
Indicates that one region is geographically located within the national boundaries of Tanzania.
-
D.
statusInZambia
Indicates the legal, social, or official standing or condition that something or someone has within the context of Zambia.
-
E.
statusInZimbabwe
Indicates the legal, social, or official standing or condition that an entity holds within the context of Zimbabwe.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69ff234e63648190a7b09a161029c8e2 |
completed | May 9, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:45 a.m.