Triple

T17655688
Position Surface form Disambiguated ID Type / Status
Subject Council of Serdica E429615 entity
Predicate heldInCity P7898 FINISHED
Object Serdica 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: Serdica | Statement: [Council of Serdica, heldInCity, Serdica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Serdica
Context triple: [Council of Serdica, heldInCity, Serdica]
  • A. Serdica chosen
    Serdica was an important ancient Roman city in the province of Thracia, located on the site of present-day Sofia, Bulgaria.
  • B. Serdika
    Serdika is the ancient name of the city now known as Sofia, the capital of Bulgaria, historically significant as a major Roman and Byzantine urban center in the Balkans.
  • C. Serdinya
    Serdinya is a small commune in the Pyrénées-Orientales department of southern France, situated in the historic region of Conflent in the eastern Pyrenees.
  • D. Kaliakra
    Kaliakra is a historic fortified headland and medieval port on Bulgaria’s Black Sea coast, renowned for its strategic cliffs and archaeological remains.
  • E. Silistra
    Silistra is a historic city in northeastern Bulgaria on the Danube River, known as an important cultural and economic center of the Dobruja region.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e40e344819086a49c69f8f2956b completed April 19, 2026, 5:55 a.m.
Created at: April 10, 2026, 6:06 a.m.