Triple

T19866666
Position Surface form Disambiguated ID Type / Status
Subject Valide Hatun E477408 entity
Predicate heldInfluenceOver P45664 FINISHED
Object Ottoman sultan 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: Ottoman sultan | Statement: [Valide Hatun, heldInfluenceOver, Ottoman sultan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldInfluenceOver
Context triple: [Valide Hatun, heldInfluenceOver, Ottoman sultan]
  • A. hasSignificantInfluenceIn
    Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
  • B. hadInfluenceOn chosen
    Indicates that one entity affected, shaped, or contributed to the development, behavior, or characteristics of another entity.
  • C. hasEnduringInfluenceOn
    Indicates that one entity exerts a lasting, long-term impact on another entity’s state, development, or behavior.
  • D. hasHistoricalInfluenceFrom
    Indicates that one entity’s characteristics, development, or significance have been shaped or affected by the past actions, ideas, or legacy of another entity.
  • E. hasRegionalInfluenceFrom
    Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
  • 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_69d8e51e7d948190aedbcd6c30361c39 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6589f9654819080597a4f7c52d64c completed April 20, 2026, 4:47 p.m.
PD Predicate disambiguation batch_69e537e8c4e481909fe95d795b4864e7 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:51 p.m.