Triple

T34275069
Position Surface form Disambiguated ID Type / Status
Subject Ludwig II. von Ungarn und Böhmen E879428 entity
Predicate GegnerInSchlachtBeiMohács P178732 FINISHED
Object Osmanisches Reich NE NERFINISHED

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: Osmanisches Reich | Statement: [Ludwig II. von Ungarn und Böhmen, GegnerInSchlachtBeiMohács, Osmanisches Reich]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: GegnerInSchlachtBeiMohács
Context triple: [Ludwig II. von Ungarn und Böhmen, GegnerInSchlachtBeiMohács, Osmanisches Reich]
  • A. opponentInBattleOfLechfeld
    Indicates that two entities were opposing sides against each other in the Battle of Lechfeld.
  • B. mainOpponentOfAustria
    Indicates that one entity is the primary rival or adversary of Austria in a given context (such as politics, war, or competition).
  • C. opponentOfByzantines
    Indicates a relationship where an entity is an adversary or enemy of the Byzantines in a conflict or rivalry.
  • D. monarchOfAustriaDuringWar
    Indicates that a person held the position of monarch of Austria during a specified war or military conflict.
  • E. strengthRussoAustrian
    Indicates the relative military or political strength between Russian and Austrian forces or interests in a given context.
  • F. None of above. chosen

Provenance (4 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_69f349b5f6648190b9420d94a4cd16e0 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f713bfdc148190a249a7874320bab8 completed May 3, 2026, 9:22 a.m.
PD Predicate disambiguation batch_69f7127884388190884f23d181a65d19 completed May 3, 2026, 9:16 a.m.
PDg Predicate description generation batch_69f7135fa2988190a20a94cfe616d754 completed May 3, 2026, 9:20 a.m.
Created at: May 1, 2026, 1:56 a.m.