Triple
T5614585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomwe |
E147444
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Cilomwe |
E147444
|
NE 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: Cilomwe | Statement: [Lomwe, hasAlternativeName, Cilomwe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cilomwe Context triple: [Lomwe, hasAlternativeName, Cilomwe]
-
A.
Soshanguve
Soshanguve is a large township in the northern part of the Gauteng province of South Africa, known for its diverse population and proximity to Pretoria.
-
B.
Lomwe
chosen
Lomwe is a Bantu language spoken primarily in Mozambique and Malawi by the Lomwe people.
-
C.
Chindau
Chindau is a Bantu language spoken primarily by the Ndau people in parts of Mozambique and Zimbabwe.
-
D.
Negombo
Negombo is a coastal city in western Sri Lanka known historically as a strategic colonial port and today for its fishing industry and beach tourism.
-
E.
Lunda
Lunda is a Bantu language spoken primarily by the Lunda people in parts of Zambia, Angola, and the Democratic Republic of the Congo.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c00905d4588190bd967842bbcf2219 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02123fa9081909086c9cce3f3e907 |
completed | March 22, 2026, 5:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a0ab9cc8190a01c5309e6cfc598 |
completed | March 22, 2026, 9:07 p.m. |
Created at: March 22, 2026, 3:39 p.m.