Triple

T10335296
Position Surface form Disambiguated ID Type / Status
Subject Council of Sirmium E242986 entity
Predicate locatedIn P40 FINISHED
Object Sirmium E36825 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: Sirmium | Statement: [Council of Sirmium, locatedIn, Sirmium]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sirmium
Context triple: [Council of Sirmium, locatedIn, Sirmium]
  • A. Sirmium chosen
    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. Carnuntum
    Carnuntum was a major Roman military camp and later a significant provincial capital and trading city on the Danube frontier in what is now eastern Austria.
  • C. Durostorum
    Durostorum was a major Roman military and urban center on the lower Danube, located in the province of Moesia (modern Silistra, Bulgaria).
  • D. Singidunum
    Singidunum was the ancient Roman and earlier Celtic settlement that occupied the site of present-day Belgrade, Serbia.
  • E. Marcianopolis
    Marcianopolis was an important ancient Roman city in the province of Moesia, known as a regional administrative and military center in the Balkans.
  • 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_69d381af787481908bc401325c760a88 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4dfc425748190a3d29f81e32e948b completed April 7, 2026, 10:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69d7505b85048190ad69a4fb5c63c677 completed April 9, 2026, 7:08 a.m.
Created at: April 6, 2026, 11:53 a.m.