Triple

T23258289
Position Surface form Disambiguated ID Type / Status
Subject Kankanay E581931 entity
Predicate alternateName P39 FINISHED
Object Kankaney NE NERFINISHED

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: Kankaney | Statement: [Kankanay, alternateName, Kankaney]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kankaney
Context triple: [Kankanay, alternateName, Kankaney]
  • A. Kankanay chosen
    Kankanay is an Austronesian language spoken by the Kankanaey people of the northern Philippines, particularly in the Cordillera region of Luzon.
  • B. Kankinara
    Kankinara is a suburban locality in West Bengal, India, known for its railway station on the Kolkata suburban network and its surrounding residential and industrial areas.
  • C. Kan'in
    Kan'in is a Japanese princely house that formed one of the collateral branches of the Imperial Family.
  • D. Kakunyo
    Kakunyo was a Japanese Buddhist monk of the Jōdo Shinshū tradition, known for systematizing his grandfather Shinran’s teachings and compiling early histories of the sect.
  • E. K’ana
    K’ana is an alternative name for Espinar Province, a highland administrative region in the Cusco Department of southern Peru known for its Andean culture and mining activities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e246079f58819085eaa9c260906880 completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f194c710c48190aff03d210642a043 completed April 29, 2026, 5:19 a.m.
Created at: April 17, 2026, 4:11 p.m.