Triple

T30426831
Position Surface form Disambiguated ID Type / Status
Subject Battle of Cyzicus E774054 entity
Predicate primaryAdversaryOfRome P16446 FINISHED
Object Mithridates VI of Pontus E69491 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: Mithridates VI of Pontus | Statement: [Battle of Cyzicus, primaryAdversaryOfRome, Mithridates VI of Pontus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryAdversaryOfRome
Context triple: [Battle of Cyzicus, primaryAdversaryOfRome, Mithridates VI of Pontus]
  • A. opponentOfByzantines
    Indicates a relationship where an entity is an adversary or enemy of the Byzantines in a conflict or rivalry.
  • B. successorAsRomanRival
    Indicates that one entity became the next primary rival of Rome after the other entity ceased to hold that role.
  • C. primaryAdversaryOfOttomans
    Indicates that one entity served as the main or most significant opponent or rival to the Ottoman Empire.
  • D. archenemyOf chosen
    Indicates a relationship in which one entity is the principal or most important enemy of another, often characterized by deep, ongoing opposition or rivalry.
  • E. primaryOpponentOfAntiochusIII
    Indicates that one entity is the main or most significant adversary or opposing force to Antiochus III.
  • F. None of above.

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_69f22491ba248190b9a4776ca8e42d02 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a0224f4b6cc8190a8f79700a9af765f completed May 11, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2870d175c081909ec6cf3cded2efbe completed June 9, 2026, 8 p.m.
PD Predicate disambiguation batch_6a0223f01eb081909419518fdd45f2a4 completed May 11, 2026, 6:46 p.m.
Created at: April 29, 2026, 8:06 p.m.