Triple
T13089852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songo-La Maya |
E310431
|
entity |
| Predicate | hasJurisdictionOver |
P808
|
FINISHED |
| Object | Songo |
E341491
|
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: Songo | Statement: [Songo-La Maya, hasJurisdictionOver, Songo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Songo Context triple: [Songo-La Maya, hasJurisdictionOver, Songo]
-
A.
Songo
chosen
Songo is a small town in Mozambique known primarily for its proximity to the Cahora Bassa Dam and its role in supporting the dam’s operations and nearby communities.
-
B.
Menongue
Menongue is a city in southeastern Angola that serves as the administrative and economic center of Cuando Cubango Province.
-
C.
Singara
Singara was an ancient fortified city in northern Mesopotamia, strategically important as a Roman-Persian frontier stronghold.
-
D.
Kasong
Kasong is an endangered Pearic language spoken by a small indigenous community in southeastern Thailand.
-
E.
Songololo
Songololo is a town in the western Democratic Republic of the Congo, situated near the border with Angola and known as a local transport and trade hub.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e27417308190b388be4a31ce4b5d |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 9:03 p.m.