Triple

T8942979
Position Surface form Disambiguated ID Type / Status
Subject Cao Kun E212948 entity
Predicate givenName P17 FINISHED
Object Kun E696702 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: Kun | Statement: [Cao Kun, givenName, Kun]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kun
Context triple: [Cao Kun, givenName, Kun]
  • A. Kun
    Kun is an alternative name for the Cumans, a historically significant nomadic Turkic people who roamed the Eurasian steppes during the Middle Ages.
  • B. Kun chosen
    Kun is a prominent high-altitude mountain peak in the Indian Himalayas, known as one of the major summits of the Nun-Kun massif in the Ladakh region.
  • C. KUN
    KUN is the IATA airport code for Kaunas Airport, a commercial international airport serving the city of Kaunas in Lithuania.
  • D. Kuni
    Kuni is the Japanese noble family name of Empress Kōjun, consort of Emperor Shōwa (Hirohito) and mother of Emperor Emeritus Akihito.
  • E. Ku
    Ku is a principal Hawaiian god associated with war, politics, and prosperity, widely venerated in traditional Native Hawaiian religion.
  • 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_69ca839694c88190b324ffeb43d23b08 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc66d93978819084b1a5c7c5dd2372 completed April 1, 2026, 12:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfc1f418708190b1272209f61e3a51 completed April 3, 2026, 1:34 p.m.
Created at: March 30, 2026, 6:58 p.m.