Triple

T6576866
Position Surface form Disambiguated ID Type / Status
Subject Kaxabu language E157187 entity
Predicate ethnicGroup P194 FINISHED
Object Kaxabu E603881 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: Kaxabu | Statement: [Kaxabu language, ethnicGroup, Kaxabu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kaxabu
Context triple: [Kaxabu language, ethnicGroup, Kaxabu]
  • A. Kaxabu chosen
    Kaxabu is an indigenous Formosan language of Taiwan traditionally spoken by the Kaxabu people.
  • B. Yakhin
    Yakhin is a variant form of the biblical name Jachin, traditionally associated with one of the two pillars of Solomon’s Temple.
  • C. Khaba
    Khaba was an early ancient Egyptian pharaoh of the 3rd Dynasty, best known for his association with the unfinished Layer Pyramid at Zawyet el'Aryan and for the relative obscurity surrounding his reign.
  • D. Kawki
    Kawki is an indigenous Andean language closely related to Aymara and spoken by a small number of people in Peru.
  • E. Urakhi
    Urakhi is a dialect of the Dargin language spoken by a subset of the Dargin people in the North Caucasus region of Russia.
  • 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_69c6882b3a108190b3a9eb343ae4162c completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae7399488190b5f6948c60188aec completed March 27, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6eedddd3c8190bd5505ba265ecf8d completed March 27, 2026, 8:55 p.m.
Created at: March 27, 2026, 1:54 p.m.