Triple

T13337629
Position Surface form Disambiguated ID Type / Status
Subject Battle of Bizerte E317738 entity
Predicate location P40 FINISHED
Object Bizerte E428105 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: Bizerte | Statement: [Battle of Bizerte, location, Bizerte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bizerte
Context triple: [Battle of Bizerte, location, Bizerte]
  • A. Biskra
    Biskra is a city in northeastern Algeria known as a gateway to the Sahara and for its date palm oases and warm winter climate.
  • B. Gafsa
    Gafsa is a historic oasis city in central Tunisia known for its ancient Roman and pre-Roman heritage and its role as a regional economic and administrative center.
  • C. Aït Bouzid
    Aït Bouzid is a town located in the mountainous Kabylie region of northern Algeria, within Tizi Ouzou Province.
  • D. Bizerte port chosen
    Bizerte port is a major Tunisian Mediterranean seaport known for its strategic location, commercial shipping activities, and naval facilities.
  • E. Mahdia
    Mahdia is a historic coastal city in present-day Tunisia that served as the first capital of the Fatimid Caliphate and an important Mediterranean trading and naval center.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99d00b75c8190af98784c7df904c8 completed April 11, 2026, 12:59 a.m.
NED1 Entity disambiguation (via context triple) batch_69f730641f588190886119506e6dde8f completed May 3, 2026, 11:24 a.m.
Created at: April 9, 2026, 9:31 p.m.