Triple

T23175155
Position Surface form Disambiguated ID Type / Status
Subject Kankana-ey E578975 entity
Predicate hasAlternativeName P39 FINISHED
Object Kankanai 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: Kankanai | Statement: [Kankana-ey, hasAlternativeName, Kankanai]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kankanai
Context triple: [Kankana-ey, hasAlternativeName, Kankanai]
  • 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. Kan'in
    Kan'in is a Japanese princely house that formed one of the collateral branches of the Imperial Family.
  • C. Kannai
    Kannai is a central district of Yokohama known for its historic port-city atmosphere, government and business centers, and mix of classic Western-style buildings and modern urban development.
  • D. Kan’onji
    Kan’onji is a coastal city in western Kagawa Prefecture on Japan’s Shikoku Island, known for its historic temples and scenic views of the Seto Inland Sea.
  • E. 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.
  • 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_69e245fd2a388190b814c0dfa15f7148 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f69cb1881909e0f47d3b32e2cb1 completed April 29, 2026, 4:56 a.m.
Created at: April 17, 2026, 4:04 p.m.