Triple

T16579131
Position Surface form Disambiguated ID Type / Status
Subject Osing language E402791 entity
Predicate hasGlottologName P6521 FINISHED
Object Osing E1220841 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: Osing | Statement: [Osing language, hasGlottologName, Osing]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Osing
Context triple: [Osing language, hasGlottologName, Osing]
  • A. Osing chosen
    Osing is an Austronesian language spoken primarily by the Osing people in the eastern part of Java, Indonesia.
  • B. Upangas
    Upangas are a group of secondary Jain scriptures that elaborate and supplement the teachings found in the primary Agamas.
  • C. Narungga
    Narungga are an Aboriginal Australian people and language group traditionally associated with the Yorke Peninsula in South Australia.
  • D. Ayawa
    Ayawa is an alternative name for the Yao people, an ethnic group found primarily in parts of East and Southern Africa.
  • E. Kambe
    Kambe is one of the Mijikenda sub-groups of the coastal Bantu peoples of Kenya, known for their distinct language and cultural traditions.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3595f9be88190b01ba628ecf1103d completed April 18, 2026, 10:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a007595cfd08190bae54d29427a1d3c completed May 10, 2026, 12:09 p.m.
Created at: April 10, 2026, 5:16 a.m.