Triple

T8448678
Position Surface form Disambiguated ID Type / Status
Subject Serdica E199745 entity
Predicate hasFormerName P65 FINISHED
Object Ulpia Serdica E320088 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: Ulpia Serdica | Statement: [Serdica, hasFormerName, Ulpia Serdica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ulpia Serdica
Context triple: [Serdica, hasFormerName, Ulpia Serdica]
  • A. Sirmium
    Sirmium was an important ancient Roman city in the province of Pannonia, serving as a major military, administrative, and imperial center in the late Roman Empire.
  • B. Durostorum
    Durostorum was a major Roman military and urban center on the lower Danube, located in the province of Moesia (modern Silistra, Bulgaria).
  • C. Aurelianum
    Aurelianum is the ancient Latin name for the French city of Orléans, reflecting its origins as a Roman settlement.
  • D. Hadrianopolis
    Hadrianopolis was an important ancient Roman and Byzantine city in Thrace, later known as Edirne in modern-day Turkey.
  • E. Ulpia chosen
    Ulpia is a Latin name element commonly associated with Roman imperial and colonial foundations, particularly linked to Emperor Trajan’s family name Ulpius.
  • 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_69ca83170f9081909cd98f55614c6476 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe445b7988190b53ae45070c70d1d completed March 31, 2026, 3:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf512d294c8190bed7e37991d237c1 completed April 3, 2026, 5:33 a.m.
Created at: March 30, 2026, 6:09 p.m.