Triple

T16532578
Position Surface form Disambiguated ID Type / Status
Subject Bizerte Lagoon E401603 entity
Predicate locatedNear P294 FINISHED
Object Bizerte E1252372 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: [Bizerte Lagoon, locatedNear, Bizerte]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bizerte
Context triple: [Bizerte Lagoon, locatedNear, Bizerte]
  • A. city of Bizerte chosen
    The city of Bizerte is a major coastal city and port in northern Tunisia, situated on the Mediterranean Sea and known for its strategic naval base and historic medina.
  • B. 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.
  • C. 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.
  • D. Aït Bouzid
    Aït Bouzid is a town located in the mountainous Kabylie region of northern Algeria, within Tizi Ouzou Province.
  • E. Bizerte port
    Bizerte port is a major Tunisian Mediterranean seaport known for its strategic location, commercial shipping activities, and naval facilities.
  • 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_69d883838abc8190bc79cb2d41733ce2 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e32ed97b0881909de106418aca8180 completed April 18, 2026, 7:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a01481c3084819099e198c408bea464 completed May 11, 2026, 3:08 a.m.
Created at: April 10, 2026, 5:15 a.m.