Triple

T10670004
Position Surface form Disambiguated ID Type / Status
Subject Kati E251461 entity
Predicate usesLanguage P238 FINISHED
Object Kati language E228811 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: Kati language | Statement: [Kati, usesLanguage, Kati language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kati language
Context triple: [Kati, usesLanguage, Kati language]
  • A. Kati language chosen
    The Kati language is a Nuristani language spoken primarily in parts of northeastern Afghanistan and adjacent regions of Pakistan.
  • B. Katu language
    Katu language is an Austroasiatic language spoken by the Katu people primarily in Laos and central Vietnam.
  • C. Nitinaht language
    The Nitinaht language is a Southern Wakashan Indigenous language spoken by the Ditidaht (Nitinaht) people of Vancouver Island in British Columbia, Canada.
  • D. Kintaq language
    The Kintaq language is a minor Aslian (Austroasiatic) language spoken by an indigenous community in Peninsular Malaysia.
  • E. Katcha language
    The Katcha language is a Kadu (Kadugli) language spoken by the Katcha people of the Nuba Mountains region in Sudan.
  • 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_69d6aa5b0d2881909584b20efc5877f0 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6f86390648190851693aedce6b7ad completed April 9, 2026, 12:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69d98865f700819093c8cadc6fcef75f completed April 10, 2026, 11:31 p.m.
Created at: April 8, 2026, 9:09 p.m.