Triple

T29671984
Position Surface form Disambiguated ID Type / Status
Subject King of Ani E750698 entity
Predicate territorialControlIncludes P111476 FINISHED
Object Ani and surrounding regions 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: Ani and surrounding regions | Statement: [King of Ani, territorialControlIncludes, Ani and surrounding regions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: territorialControlIncludes
Context triple: [King of Ani, territorialControlIncludes, Ani and surrounding regions]
  • A. territoryIncluded
    Indicates that one territory is geographically or administratively contained within another territory.
  • B. territoryOriginallyIncluded
    Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
  • C. territorialJurisdictionIncludes chosen
    Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
  • D. mainTerritoryOfInfluence
    Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
  • E. territorialExtent
    Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
  • 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_69f0d62418a08190a401b127adf9f8a6 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f697eabb048190bc01a830f14942c6 completed May 3, 2026, 12:33 a.m.
PD Predicate disambiguation batch_69f69664142c8190bc695501056b0236 completed May 3, 2026, 12:27 a.m.
Created at: April 28, 2026, 7:05 p.m.