Triple

T16428180
Position Surface form Disambiguated ID Type / Status
Subject Canaan City E398998 entity
Predicate appliedTo P1129 FINISHED
Object Calabar E87286 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: Calabar | Statement: [Canaan City, appliedTo, Calabar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Calabar
Context triple: [Canaan City, appliedTo, Calabar]
  • A. Calabar chosen
    Calabar is a historic port city in southeastern Nigeria known for its role in the transatlantic slave trade and its vibrant cultural festivals.
  • B. Ebolowa
    Ebolowa is a city in southern Cameroon that serves as an administrative and commercial center for the surrounding agricultural region.
  • C. Ewondo
    Ewondo is a Bantu language spoken primarily by the Ewondo people in central Cameroon, including in and around the capital city, Yaoundé.
  • D. Nkawkaw
    Nkawkaw is a major commercial town and transport hub in southern Ghana, located along the Accra–Kumasi highway at the base of the Kwahu Plateau.
  • E. Benina
    Benina is a town in eastern Libya that serves as the main gateway to the nearby city of Benghazi through its international airport.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328fc223c8190bbed29907351a6f6 completed April 18, 2026, 6:47 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007d9c8de4819093ae3901cf0c8805 completed May 10, 2026, 12:44 p.m.
Created at: April 10, 2026, 5:09 a.m.