Triple

T6671536
Position Surface form Disambiguated ID Type / Status
Subject Battle of Homs (1281) E151740 entity
Predicate aimOfIlkhanate P64674 FINISHED
Object to seize Syria from the Mamluks 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: to seize Syria from the Mamluks | Statement: [Battle of Homs (1281), aimOfIlkhanate, to seize Syria from the Mamluks]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfIlkhanate
Context triple: [Battle of Homs (1281), aimOfIlkhanate, to seize Syria from the Mamluks]
  • A. strategicObjectiveOttoman
    Indicates that one entity serves as or relates to a strategic objective or goal specifically concerning the Ottoman Empire.
  • B. aimOfRome
    Indicates that something is the goal, purpose, or intended objective of Rome.
  • C. caliphate
    Indicates a relationship in which an authority or governance structure is organized under a caliph, claiming religious and political leadership over a Muslim community or territory.
  • D. primaryTacticOttomans
    Indicates the main military or strategic method predominantly employed by the Ottoman forces in a given conflict or context.
  • E. aimOf chosen
    Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
  • 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_69c687f71fc081909dbd45d6377f6045 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6ce738fe88190a5557900efeec7ec completed March 27, 2026, 6:37 p.m.
PD Predicate disambiguation batch_69c6ad09974c81908784300ae218961f completed March 27, 2026, 4:15 p.m.
Created at: March 27, 2026, 2:03 p.m.