Triple

T20797767
Position Surface form Disambiguated ID Type / Status
Subject Juhar dialect E511955 entity
Predicate isVarietyOf P2074 FINISHED
Object Karo language 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: Karo language | Statement: [Juhar dialect, isVarietyOf, Karo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karo language
Context triple: [Juhar dialect, isVarietyOf, Karo language]
  • A. Karo language chosen
    Karo language is an Austronesian language spoken by the Karo Batak people of North Sumatra, Indonesia.
  • B. Karo language
    Karo language is an indigenous Tupian language spoken by the Karo people of the Brazilian Amazon, known for its endangered status and significance in studies of South American linguistic diversity.
  • C. Karao language
    The Karao language is an Austronesian language spoken by the Karao people in the Cordillera region of northern Luzon in the Philippines.
  • D. Karkin language
    The Karkin language is an extinct Ohlone (Costanoan) Native American language once spoken in the San Francisco Bay Area of California.
  • E. Karata language
    The Karata language is a Northeast Caucasian language spoken by the Karata people in the Republic of Dagestan, Russia.
  • 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_69e0b4cc69f481908e98751e697b9df4 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2ae2c4c819087f620df31dc1aba completed April 21, 2026, 12:19 a.m.
Created at: April 16, 2026, 12:39 p.m.