Triple

T23899776
Position Surface form Disambiguated ID Type / Status
Subject Battle of Angora E601008 entity
Predicate TimuridAllies P136406 FINISHED
Object Anatolian beyliks opposed to Ottomans LITERAL 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: Anatolian beyliks opposed to Ottomans | Statement: [Battle of Angora, TimuridAllies, Anatolian beyliks opposed to Ottomans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: TimuridAllies
Context triple: [Battle of Angora, TimuridAllies, Anatolian beyliks opposed to Ottomans]
  • A. successorAsMughalAlly
    Indicates that one entity becomes the next political or military ally of the Mughal power, taking over that allied role from another entity.
  • B. relationshipToTimur
    Indicates the type or nature of the relationship that one entity has to Timur.
  • C. primaryAdversaryOfOttomans
    Indicates that one entity served as the main or most significant opponent or rival to the Ottoman Empire.
  • D. alliesOf chosen
    Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
  • E. vassalOrAllyOf
    Indicates that one entity is subordinate to, dependent on, or formally aligned in support of another entity, typically in a hierarchical or cooperative political or military relationship.
  • F. None of above.

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_69e295341ac0819080647f2908af793c completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cdddca088190b6c26df984a143ad completed April 29, 2026, 9:22 a.m.
PD Predicate disambiguation batch_69f1614e24b48190a1c8fb5b7c75ee0f completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:25 p.m.