Triple

T19368788
Position Surface form Disambiguated ID Type / Status
Subject Emirate of Bari E484475 entity
Predicate capital P234 FINISHED
Object Bari 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: Bari | Statement: [Emirate of Bari, capital, Bari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bari
Context triple: [Emirate of Bari, capital, Bari]
  • A. Bari
    Bari is a Nilotic ethnic group primarily inhabiting South Sudan and neighboring regions, known for their agro-pastoral lifestyle and distinctive language within the Eastern Nilotic branch.
  • B. Bari chosen
    Bari is a major port city in southern Italy that served as an important Allied military hub and logistics center during World War II.
  • C. Brindisi
    Brindisi is a historic port city in southern Italy’s Apulia region, long serving as a key maritime gateway between Italy and the eastern Mediterranean.
  • D. Pescara
    Pescara is a coastal city in the Abruzzo region of central Italy, known for its Adriatic beaches, modern urban layout, and role as a commercial and tourist hub.
  • E. Ancona
    Ancona is a historic port city on Italy’s Adriatic coast, notable for its long-standing Jewish community and role as a commercial and cultural crossroads.
  • 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619ae6838819080584d60cbd58bbd completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:35 p.m.