Triple

T18890443
Position Surface form Disambiguated ID Type / Status
Subject Battle of Kissoué E462071 entity
Predicate locatedIn P40 FINISHED
Object Kissoué 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: Kissoué | Statement: [Battle of Kissoué, locatedIn, Kissoué]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kissoué
Context triple: [Battle of Kissoué, locatedIn, Kissoué]
  • A. Kissoué chosen
    Kissoué is a town in southwestern Syria that gained historical significance as the site of a notable World War II battle during the Syria–Lebanon campaign.
  • B. Koussassé
    Koussassé is an alternative name for the Kusaal language, a Gur language spoken primarily in northern Ghana and parts of Burkina Faso.
  • C. Oussouye
    Oussouye is a town in southern Senegal’s Casamance region, known for its Jola culture and as a center of local traditions and languages.
  • D. Ngoumbi
    Ngoumbi is an alternative name for the Kombe people, an ethnic group of Central Africa.
  • E. N’Guigmi
    N’Guigmi is a town and commune in southeastern Niger, located near Lake Chad and serving as an important local center for trade and transport.
  • 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_69d8dcfc3430819095ee6fc0eb4c06a5 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c47ab34c8190bfb69444a5263538 completed April 20, 2026, 6:15 a.m.
Created at: April 10, 2026, 11:58 a.m.