Triple

T6301176
Position Surface form Disambiguated ID Type / Status
Subject Rejang languages E141257 entity
Predicate writingSystem P454 FINISHED
Object Rejang script E403694 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: Rejang script | Statement: [Rejang languages, writingSystem, Rejang script]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rejang script
Context triple: [Rejang languages, writingSystem, Rejang script]
  • A. Rejang script chosen
    Rejang script is an indigenous Brahmic-derived writing system used primarily for the Rejang language of southwestern Sumatra, Indonesia.
  • B. Lontara script
    The Lontara script is an indigenous writing system traditionally used by the Bugis and Makassarese peoples of South Sulawesi, Indonesia, to write their Austronesian languages.
  • C. Batak script
    Batak script is an indigenous writing system from northern Sumatra historically used to write the various Batak languages.
  • D. Sundanese script
    The Sundanese script is an abugida used historically and in modern times to write the Sundanese language of West Java, Indonesia.
  • E. Jawi script
    Jawi script is an Arabic-based writing system historically used for various Malayic languages in Southeast Asia, including Minangkabau, for religious, literary, and administrative purposes.
  • 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_69c008cf0ad4819095def81e2bd42f9f completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0645bb41481909294b06e2b3e1845 completed March 22, 2026, 9:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c5e42f38bc819086a3e66a83ffc792 completed March 27, 2026, 1:58 a.m.
Created at: March 22, 2026, 4:27 p.m.