Triple

T11204762
Position Surface form Disambiguated ID Type / Status
Subject Silistra E265131 entity
Predicate historicalName P65 FINISHED
Object Durostorum E217470 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: Durostorum | Statement: [Silistra, historicalName, Durostorum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Durostorum
Context triple: [Silistra, historicalName, Durostorum]
  • A. Durostorum chosen
    Durostorum was a major Roman military and urban center on the lower Danube, located in the province of Moesia (modern Silistra, Bulgaria).
  • B. Ulpia
    Ulpia is a Latin name element commonly associated with Roman imperial and colonial foundations, particularly linked to Emperor Trajan’s family name Ulpius.
  • C. Aurelianum
    Aurelianum is the ancient Latin name for the French city of Orléans, reflecting its origins as a Roman settlement.
  • D. Diocaesarea
    Diocaesarea is the Roman-era name for the ancient Galilean city of Sepphoris, a major administrative and cultural center near Nazareth.
  • E. Ulpia Severina
    Ulpia Severina was a Roman empress of the 3rd century, notable as the wife of Emperor Aurelian and possibly a brief ruler in her own right after his death.
  • 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_69d6aa9eb9248190b20211772621b4bc completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d355c481908fc3d555b596314d completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4ad0984e08190af9c8263cc2a079d completed April 19, 2026, 10:23 a.m.
Created at: April 8, 2026, 9:30 p.m.