Triple

T10269089
Position Surface form Disambiguated ID Type / Status
Subject Vannius E240787 entity
Predicate predecessor P97 FINISHED
Object Maroboduus E236306 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: Maroboduus | Statement: [Vannius, predecessor, Maroboduus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maroboduus
Context triple: [Vannius, predecessor, Maroboduus]
  • A. Maroboduus chosen
    Maroboduus was a 1st-century AD king of the Marcomanni who established a powerful Germanic kingdom in Bohemia and was a notable contemporary and rival of the Roman Empire.
  • B. Ariovistus
    Ariovistus was a Germanic king and military leader who famously clashed with Julius Caesar during the Gallic Wars in the 1st century BC.
  • C. Viriatus
    Viriatus was a famed Lusitanian leader and guerrilla commander who resisted Roman expansion in the Iberian Peninsula during the 2nd century BCE.
  • D. Ahenobarbus
    Ahenobarbus was the cognomen of a prominent Roman aristocratic family line to which the emperor Nero belonged.
  • E. Burebista
    Burebista was a 1st-century BC king who forged a powerful Dacian kingdom in the Carpathian region and became a significant regional rival to Rome.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d27033c081908721f6f8568059f2 completed April 7, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69d6f80c25888190a3e8a2c513df7043 completed April 9, 2026, 12:51 a.m.
Created at: April 6, 2026, 11:35 a.m.