Triple

T31584589
Position Surface form Disambiguated ID Type / Status
Subject Azerbaijani Turks E805920 entity
Predicate historicalEmpireContext P165574 FINISHED
Object Safavid Empire 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: Safavid Empire | Statement: [Azerbaijani Turks, historicalEmpireContext, Safavid Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalEmpireContext
Context triple: [Azerbaijani Turks, historicalEmpireContext, Safavid Empire]
  • A. historicalEmpireCenter
    Indicates that a location served as the primary political or administrative center of a historical empire.
  • B. hasHistoricalEmpire
    Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
  • C. historicalRegionOfInfluence
    Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
  • D. historicalBackground
    Indicates that one entity provides contextual historical information or circumstances that help explain the origin, development, or significance of another entity.
  • E. empireContext chosen
    Indicates that one entity exists, acts, or is interpreted within the political, cultural, or historical framework of a particular empire.
  • 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_69f348d4891c8190b02bae3c8ecb68b7 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69ff49f888348190b9c55afa73b99e6a completed May 9, 2026, 2:51 p.m.
PD Predicate disambiguation batch_69ff49614ef88190ac70b034c55ad738 completed May 9, 2026, 2:49 p.m.
Created at: April 30, 2026, 10:25 p.m.