Triple

T20856819
Position Surface form Disambiguated ID Type / Status
Subject Karo people E513501 entity
Predicate traditionalBelief P13958 FINISHED
Object Pemena 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: Pemena | Statement: [Karo people, traditionalBelief, Pemena]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pemena
Context triple: [Karo people, traditionalBelief, Pemena]
  • A. Pemena chosen
    Pemena is the indigenous traditional belief system of the Karo people of the Karo Highlands in North Sumatra, Indonesia, encompassing their ancestral cosmology, rituals, and spiritual practices.
  • B. Pemper
    Pemper is a surname most notably associated with Mietek Pemper, a Holocaust survivor who helped compile Oskar Schindler’s list.
  • C. Penneru
    Penneru is an alternate name for the Penna River, a major river flowing through the southern Indian states of Andhra Pradesh and Karnataka.
  • D. Danglas
    Danglas is a rural municipality in the province of Abra in the Cordillera region of the Philippines.
  • E. Lehae
    Lehae is a residential suburb located in the southern part of Johannesburg, South Africa.
  • 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_69e0b4f5b01081909452f654d2fc3f50 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3a93ea881909b9f80a9bd0605b6 completed April 21, 2026, 12:24 a.m.
Created at: April 16, 2026, 12:44 p.m.