Triple

T22113299
Position Surface form Disambiguated ID Type / Status
Subject Ngamprah E546470 entity
Predicate hasLanguage P15 FINISHED
Object Sundanese 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: Sundanese | Statement: [Ngamprah, hasLanguage, Sundanese]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sundanese
Context triple: [Ngamprah, hasLanguage, Sundanese]
  • A. Sundanese chosen
    The Sundanese are an indigenous ethnic group of western Java in Indonesia, known for their distinct language, rich musical and dance traditions, and agrarian culture.
  • B. East Sumbanese
    East Sumbanese is an Austronesian language spoken on the eastern part of Sumba Island in Indonesia.
  • C. Banjarese
    Banjarese is an Austronesian language spoken primarily by the Banjar people of South Kalimantan in Indonesia.
  • D. Madurese
    The Madurese are an Austronesian ethnic group from Madura Island and surrounding regions of Indonesia, known for their distinct language, Islamic traditions, and maritime and cattle-breeding culture.
  • E. Papuan Malay
    Papuan Malay is an eastern Indonesian variety of Malay used as a lingua franca in Papua, characterized by distinctive phonological and grammatical features influenced by local Papuan languages.
  • 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1294b9d5c8190897b760ca4f3b09a completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.