Triple

T5326616
Position Surface form Disambiguated ID Type / Status
Subject Batak script E123201 entity
Predicate hasVariant P455 FINISHED
Object Karo Batak script E123201 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: Karo Batak script | Statement: [Batak script, hasVariant, Karo Batak script]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Karo Batak script
Context triple: [Batak script, hasVariant, Karo Batak script]
  • A. Batak script chosen
    Batak script is an indigenous writing system from northern Sumatra historically used to write the various Batak languages.
  • B. Rejang script
    Rejang script is an indigenous Brahmic-derived writing system used primarily for the Rejang language of southwestern Sumatra, Indonesia.
  • C. Sundanese script
    The Sundanese script is an abugida used historically and in modern times to write the Sundanese language of West Java, Indonesia.
  • D. 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.
  • E. Tagbanwa script
    Tagbanwa script is an indigenous Brahmic-derived writing system historically used by the Tagbanwa people of Palawan in the Philippines to write their native languages.
  • 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_69bd46477f9081909d242a327d749466 completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd85912d24819093cc405bebe8e870 completed March 20, 2026, 5:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf21bba3f8819085efcb9d75fea1f9 completed March 21, 2026, 10:54 p.m.
Created at: March 20, 2026, 2 p.m.