Triple

T30022394
Position Surface form Disambiguated ID Type / Status
Subject Battle of Bash Abaran E762781 entity
Predicate objectiveOfOttomanForces P70778 FINISHED
Object advance toward Yerevan 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: advance toward Yerevan | Statement: [Battle of Bash Abaran, objectiveOfOttomanForces, advance toward Yerevan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: objectiveOfOttomanForces
Context triple: [Battle of Bash Abaran, objectiveOfOttomanForces, advance toward Yerevan]
  • A. strategicObjectiveOttoman chosen
    Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
  • B. primaryTacticOttomans
    Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
  • C. outcomeForOttomans
    Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
  • D. OttomanForcesIncluded
    Indicates that the composition of a military force or contingent included units or personnel from the Ottoman forces.
  • E. OttomanStrength
    Indicates the level or degree of military, political, or economic power possessed or exerted by the Ottoman Empire in a given context.
  • 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_69f2246ee6e48190b69e837b913b398a completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f679a7eb208190a85a8e61f45ba832 completed May 2, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69f66ec9919881908a187bfc7c4df192 completed May 2, 2026, 9:38 p.m.
Created at: April 29, 2026, 6:47 p.m.