Triple
T18375615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Konna |
E446305
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Konna |
—
|
NE NERFINISHED |
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: Konna | Statement: [Battle of Konna, location, Konna]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Konna Context triple: [Battle of Konna, location, Konna]
-
A.
Konna
chosen
Konna is a town in central Mali that gained prominence as a strategic battleground during the 2013 conflict between Malian and Islamist forces.
-
B.
Konna
Konna is the local name for Cassia fistula, a tropical ornamental tree known for its striking cascades of bright yellow flowers.
-
C.
Kono
Kono is a Japanese surname most prominently associated with politician Taro Kono, a leading figure in contemporary Japanese politics.
-
D.
Kono
Kono is a major Mande language spoken primarily in parts of West Africa, notably in Sierra Leone and neighboring regions.
-
E.
Jukun Kona
Jukun Kona is a distinct subgroup of the Jukun people, an ethnic community primarily found in parts of central Nigeria.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51759353481908aa2de599fd2cf3b |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 10:45 a.m.