Triple

T5601153
Position Surface form Disambiguated ID Type / Status
Subject Jhala dynasty E147122 entity
Predicate ruled P760 FINISHED
Object Lakhtar State E106302 NE 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: Lakhtar State | Statement: [Jhala dynasty, ruled, Lakhtar State]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lakhtar State
Context triple: [Jhala dynasty, ruled, Lakhtar State]
  • A. Ngaraard State
    Ngaraard State is one of the states of Palau, located on the island of Babeldaob and known for its traditional villages and coastal landscapes.
  • B. Geokchay Uyezd
    Geokchay Uyezd was an administrative district of the Russian Empire and early Soviet period located in the central part of present-day Azerbaijan.
  • C. Jasdan State chosen
    Jasdan State was a former princely state in western India historically governed by the Jadeja Rajput dynasty.
  • D. Karakalpak
    Karakalpak is a Turkic language spoken primarily by the Karakalpak people in northwestern Uzbekistan and surrounding regions.
  • E. Kumyks
    The Kumyks are a Turkic-speaking ethnic group native to the northeastern Caucasus, primarily in Dagestan, with a distinct language, culture, and history shaped by both steppe and Caucasian influences.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c009043d648190a7af89698ccf1e3e completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c020da519c81908626b243e40db263 completed March 22, 2026, 5:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c02873b1dc8190b11a6c069f3e4f7e completed March 22, 2026, 5:35 p.m.
Created at: March 22, 2026, 3:39 p.m.