Triple

T7415373
Position Surface form Disambiguated ID Type / Status
Subject Royal Palaces of Abomey E171114 entity
Predicate locatedIn P40 FINISHED
Object Abomey E178859 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: Abomey | Statement: [Royal Palaces of Abomey, locatedIn, Abomey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Abomey
Context triple: [Royal Palaces of Abomey, locatedIn, Abomey]
  • A. Abomey chosen
    Abomey is a historic city in southern Benin that served as the capital of the powerful Kingdom of Dahomey and is renowned for its royal palaces and cultural heritage.
  • B. Ouidah
    Ouidah is a coastal city in Benin historically known as a major center of the transatlantic slave trade and for its rich Vodun (Voodoo) cultural heritage.
  • C. Lomé
    Lomé is the coastal capital and largest city of Togo, serving as a key economic and cultural hub in West Africa.
  • D. Cabira
    Cabira was an ancient city in the region of Pontus in Asia Minor, later known as Neocaesarea under Roman rule.
  • E. Bignona
    Bignona is a town in southern Senegal’s Casamance region, known as a local center of trade and cultural diversity.
  • 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_69c68a618bdc81908d8018edadecd1a4 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f2c643248190a387abba2f482b25 completed March 27, 2026, 9:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c81ee1b48c81909912ff0d7bf2837e completed March 28, 2026, 6:33 p.m.
Created at: March 27, 2026, 3:11 p.m.