Triple

T16579813
Position Surface form Disambiguated ID Type / Status
Subject Breuci E402799 entity
Predicate leader P981 FINISHED
Object Bato of the Breuci E402796 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: Bato of the Breuci | Statement: [Breuci, leader, Bato of the Breuci]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bato of the Breuci
Context triple: [Breuci, leader, Bato of the Breuci]
  • A. Bato the Breucian chosen
    Bato the Breucian was an Illyrian chieftain who led the Breuci tribe in a major uprising against Roman rule during the Great Illyrian Revolt in the early 1st century AD.
  • B. Bato the Daesitiate
    Bato the Daesitiate was an Illyrian chieftain who led a major uprising against Roman rule during the Great Illyrian Revolt in the early 1st century AD.
  • C. Dulo
    Dulo was the early medieval ruling dynasty of the Bulgars, traditionally associated with Khan Asparuh and the founding of the First Bulgarian Empire.
  • D. Baldovino
    Baldovino is an Italian given name, historically used in medieval Europe and related to the name Baldwin.
  • E. Amarildo
    Amarildo is a former Brazilian footballer best known as a forward who starred for Botafogo and the Brazil national team in the early 1960s.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35960834c819080eed0c9f32b881d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0084b077f481909796b5b60f501239 completed May 10, 2026, 1:14 p.m.
Created at: April 10, 2026, 5:16 a.m.