Triple

T22175897
Position Surface form Disambiguated ID Type / Status
Subject Cakap Pakpak E548048 entity
Predicate hasAlternativeName P39 FINISHED
Object Pakpak Dairi 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: Pakpak Dairi | Statement: [Cakap Pakpak, hasAlternativeName, Pakpak Dairi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pakpak Dairi
Context triple: [Cakap Pakpak, hasAlternativeName, Pakpak Dairi]
  • A. Pakpak-Dairi chosen
    Pakpak-Dairi is an Austronesian language spoken by the Pakpak (Dairi) people of northern Sumatra, Indonesia.
  • B. Toba Batak
    Toba Batak is an Austronesian language spoken primarily by the Toba Batak people of North Sumatra, Indonesia.
  • C. Bukit Lawang
    Bukit Lawang is a riverside village in North Sumatra, Indonesia, best known as a gateway to Gunung Leuser National Park and a popular spot for viewing Sumatran orangutans in the wild.
  • D. Muaro Sijunjung
    Muaro Sijunjung is the main administrative and urban center of Sijunjung Regency in West Sumatra, Indonesia.
  • E. Kepahiang
    Kepahiang is a region in Bengkulu, Sumatra, Indonesia, historically associated with the Rejang people and their traditional Rejang script.
  • 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_69e11e3d53f88190a2b690e3f25bb062 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a6c40988190ba52ea46079eb306 completed April 28, 2026, 9:45 p.m.
Created at: April 16, 2026, 8:34 p.m.