Triple

T28832359
Position Surface form Disambiguated ID Type / Status
Subject Armenian-Ottoman conflicts E728083 entity
Predicate hasStateActor P65960 FINISHED
Object Ottoman government 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: Ottoman government | Statement: [Armenian-Ottoman conflicts, hasStateActor, Ottoman government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStateActor
Context triple: [Armenian-Ottoman conflicts, hasStateActor, Ottoman government]
  • A. isNonStateActor
    Indicates that the entity operates independently of any sovereign state’s formal governmental authority, rather than as an official arm of a state.
  • B. hasStateSystem
    Indicates that an entity possesses, follows, or is governed by a particular system of state organization, rules, or governance.
  • C. hasMemberState
    Indicates that an entity includes or comprises another entity as one of its constituent member states within a larger organizational or political structure.
  • D. hasStatePowers chosen
    Indicates that an entity possesses or exercises the official powers or authorities of a state-level government.
  • E. hasKeyActor
    Indicates that an entity plays a primary or central role (a key actor) in relation to another entity or 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_69f0319dc6088190bbfaa206d40ed74a completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69fd68abf52881909c5a390c362b7c59 completed May 8, 2026, 4:38 a.m.
PD Predicate disambiguation batch_69fd6812d0c88190930d8fa2d4b92490 completed May 8, 2026, 4:35 a.m.
Created at: April 28, 2026, 6:38 a.m.