Triple

T9577654
Position Surface form Disambiguated ID Type / Status
Subject Rote languages E231084 entity
Predicate hasPart P35 FINISHED
Object Lolein language E809242 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: Lolein language | Statement: [Rote languages, hasPart, Lolein language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lolein language
Context triple: [Rote languages, hasPart, Lolein language]
  • A. Lole language chosen
    Lole is an Austronesian language spoken on Rote Island in Indonesia, known for its role in the Rote languages group.
  • B. Lemolang language
    Lemolang is an Austronesian language spoken by a small community in South Sulawesi, Indonesia.
  • C. Lusei language
    The Lusei language is a Kuki-Chin language of the Tibeto-Burman family spoken primarily by the Lusei (Mizo) people in northeastern India, especially in Mizoram.
  • D. Lewa language
    Lewa language is an Austronesian language spoken by the Sumba people on Sumba Island in eastern Indonesia.
  • E. Sa’och language
    The Sa’och language is an endangered Austroasiatic language spoken by the Sa’och people of Cambodia and Thailand, belonging to the Pearic branch.
  • 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_69ca848091c48190bc313d6620d09555 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd99ad7d108190a0b8c975351ea727 completed April 1, 2026, 10:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69d17907de488190be97e58b05b6c6f2 completed April 4, 2026, 8:48 p.m.
Created at: March 30, 2026, 8:05 p.m.