Triple

T22615732
Position Surface form Disambiguated ID Type / Status
Subject beylerbey E558139 entity
Predicate wasReplacedGraduallyBy P110612 FINISHED
Object vali (governor) in later Ottoman period 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: vali (governor) in later Ottoman period | Statement: [beylerbey, wasReplacedGraduallyBy, vali (governor) in later Ottoman period]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasReplacedGraduallyBy
Context triple: [beylerbey, wasReplacedGraduallyBy, vali (governor) in later Ottoman period]
  • A. wasSupersededBy
    Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
  • B. partlyReplacedBy
    Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
  • C. placedBy
    Indicates that one entity was positioned, set, or put in a location or context by another entity.
  • D. oftenReplacedBy
    Indicates that one entity is frequently substituted or superseded by another in similar contexts or uses.
  • E. indirectlyReplacedBy chosen
    Indicates that one entity has been superseded or taken over by another entity through one or more intermediate replacements, rather than by a direct, immediate substitution.
  • 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_69e24545a8e08190bfa7482a2c725ff1 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f167edec2481909c2f06607b3cb8f6 completed April 29, 2026, 2:07 a.m.
PD Predicate disambiguation batch_69ee62855558819080da946c7b35a160 completed April 26, 2026, 7:07 p.m.
Created at: April 17, 2026, 2:59 p.m.