Triple

T3235894
Position Surface form Disambiguated ID Type / Status
Subject Battle of Adrianople (378) E67853 entity
Predicate commander P1061 FINISHED
Object Fritigern E233960 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: Fritigern | Statement: [Battle of Adrianople (378), commander, Fritigern]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fritigern
Context triple: [Battle of Adrianople (378), commander, Fritigern]
  • A. Fritigern chosen
    Fritigern was a 4th-century Visigothic leader best known for leading Gothic forces against the Eastern Roman Empire, including at the Battle of Adrianople.
  • B. Rigmor
    Rigmor is a feminine given name of Scandinavian origin, particularly used in Norway and Denmark.
  • C. Aduard
    Aduard is a village in the Dutch province of Groningen, known historically for its medieval Cistercian monastery and its location near the city of Groningen.
  • D. Raginmund
    Raginmund is a Germanic personal name of early medieval origin that later evolved into forms such as the Spanish given name Ramón.
  • E. Gaheris
    Gaheris is a knight of the Round Table in Arthurian legend, known as one of King Arthur’s nephews and a member of the Orkney clan.
  • 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_69ad858d27348190abb61c280b4c86a9 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adaee05d34819095dbce4db6ac8613 completed March 8, 2026, 5:16 p.m.
NED1 Entity disambiguation (via context triple) batch_69b277459d1081909766934ce6a56091 completed March 12, 2026, 8:20 a.m.
Created at: March 8, 2026, 3:08 p.m.