Triple
T7152170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilongwe |
E166716
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Lilongwe River |
E481383
|
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: Lilongwe River | Statement: [Lilongwe, namedAfter, Lilongwe River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lilongwe River Context triple: [Lilongwe, namedAfter, Lilongwe River]
-
A.
Lilongwe River
chosen
The Lilongwe River is a significant river in Malawi that flows through the capital city, Lilongwe, before ultimately draining into Lake Malawi.
-
B.
Lusaka River
The Lusaka River is a watercourse in Zambia that gave its name to the nation’s capital city, Lusaka.
-
C.
Lisungwe River
The Lisungwe River is a tributary watercourse in southern Malawi that feeds into the Shire River within the Zambezi River basin.
-
D.
Lukuga River
The Lukuga River is a major river in central Africa that drains Lake Tanganyika westward toward the Congo River basin.
-
E.
Pungwe River
The Pungwe River is a major watercourse in southeastern Africa that flows from Zimbabwe into Mozambique, supporting regional ecosystems, agriculture, and hydropower.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7f3e4a88190a3110f2368262528 |
completed | March 27, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8de8efd648190b70b4299ecae32c7 |
completed | March 29, 2026, 8:10 a.m. |
Created at: March 27, 2026, 2:46 p.m.