Triple

T18832830
Position Surface form Disambiguated ID Type / Status
Subject Bandung–Banjar railway E460577 entity
Predicate endPoint P390 FINISHED
Object Banjar 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 | Statement: [Bandung–Banjar railway, endPoint, Banjar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banjar
Context triple: [Bandung–Banjar railway, endPoint, Banjar]
  • A. 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.
  • B. Banjar chosen
    Banjar is a city in the eastern part of West Java, Indonesia, known as a regional transit hub connecting West Java with Central Java.
  • C. 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.
  • D. Banjar Regency
    Banjar Regency is an administrative region in South Kalimantan, Indonesia, known for its traditional river-based culture and iconic floating markets.
  • E. The Padang
    The Padang is a historic open field in Singapore’s civic district that has long served as a central venue for major national ceremonies, celebrations, and public events.
  • 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_69d8dcf94c288190a06dea029ae4b223 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5a99b540c8190a29e5f9d56791d41 completed April 20, 2026, 4:20 a.m.
Created at: April 10, 2026, 11:56 a.m.