Triple

T17948320
Position Surface form Disambiguated ID Type / Status
Subject Kaykaus II E448761 entity
Predicate governmentUnder P89122 FINISHED
Object Mongol suzerainty 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: Mongol suzerainty | Statement: [Kaykaus II, governmentUnder, Mongol suzerainty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: governmentUnder
Context triple: [Kaykaus II, governmentUnder, Mongol suzerainty]
  • A. underGovernment chosen
    Indicates that one entity is subject to the authority, control, or jurisdiction of a particular government.
  • B. governmentOf
    Indicates that one entity serves as the governing authority or administrative body of another entity, typically a state, region, or organization.
  • C. governmentAtTime
    Indicates that a specified government is in power or holds authority over a given entity during a particular time or time interval.
  • D. governmentInPower
    Indicates that a particular government currently holds official authority and is exercising ruling power over a state or region.
  • E. mainGovernment
    Indicates that one entity serves as the primary governing authority or central government for 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afa9cb2481908c95f8c430dcc0aa completed April 19, 2026, 10:34 a.m.
PD Predicate disambiguation batch_69e3f8f2bd088190b1e22ad4d9cc8b13 completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:21 a.m.