Triple

T22689282
Position Surface form Disambiguated ID Type / Status
Subject Banjarese E561004 entity
Predicate hasStandardVariety P751 FINISHED
Object Banjar Kuala 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: Banjar Kuala | Statement: [Banjarese, hasStandardVariety, Banjar Kuala]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banjar Kuala
Context triple: [Banjarese, hasStandardVariety, Banjar Kuala]
  • A. Banjar Kuala chosen
    Banjar Kuala is a regional dialect of the Banjarese language spoken primarily in and around the city of Banjarmasin in South Kalimantan, Indonesia.
  • B. Banjar Bakumpai
    Banjar Bakumpai is a regional dialect of the Banjarese language spoken by the Bakumpai community in parts of Kalimantan, Indonesia.
  • C. Banjar
    Banjar are an indigenous ethnic group of South Kalimantan in Indonesian Borneo, known for their Malay-influenced culture, river-based settlements, and historical role in regional trade and sultanates.
  • D. Banjar
    Banjar is a city in the eastern part of West Java, Indonesia, known as a regional transit hub connecting West Java with Central Java.
  • E. Banjar
    Banjar is a small town in Himachal Pradesh, India, known as a gateway to the Great Himalayan National Park and the scenic Tirthan Valley.
  • 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_69e2454d71b48190a1f80af9f82b6fcf completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1789931148190925ce9038c16413b completed April 29, 2026, 3:18 a.m.
Created at: April 17, 2026, 3:13 p.m.