Triple

T22734184
Position Surface form Disambiguated ID Type / Status
Subject South Sulawesi kingdoms E562219 entity
Predicate includedKingdom P12466 FINISHED
Object Luwu 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: Luwu | Statement: [South Sulawesi kingdoms, includedKingdom, Luwu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Luwu
Context triple: [South Sulawesi kingdoms, includedKingdom, Luwu]
  • A. Rejang
    Rejang are an indigenous ethnic group of southwestern Sumatra, Indonesia, known for their distinct Austronesian language and traditional Rejang script.
  • B. Luwu Regency chosen
    Luwu Regency is an administrative region in South Sulawesi, Indonesia, known for its coastal and mountainous landscapes and its role as part of the historical Luwu Kingdom area.
  • C. Teluk Bone
    Teluk Bone is a large gulf on the eastern side of Sulawesi Island in Indonesia, known for its rich marine biodiversity and important fishing grounds.
  • D. Bolango-Bulango
    Bolango-Bulango is an Austronesian language spoken by the Bolango people in northern Sulawesi, Indonesia.
  • E. Tanjungpura
    Tanjungpura is a historical kingdom in western Borneo, often associated with early Malay and Dayak polities in the region.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1796e4970819090fb9c9926673938 completed April 29, 2026, 3:22 a.m.
Created at: April 17, 2026, 3:22 p.m.