Triple

T18115802
Position Surface form Disambiguated ID Type / Status
Subject Oberpfalz E433601 entity
Predicate contains P35 FINISHED
Object Cham 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: Cham | Statement: [Oberpfalz, contains, Cham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cham
Context triple: [Oberpfalz, contains, Cham]
  • A. Cham chosen
    Cham is a town in the Upper Palatinate region of Bavaria, Germany, known for its location along the Regen River and its historical role as a regional center.
  • B. Cham
    The Cham are an Austronesian ethnic group of Southeast Asia, historically associated with the ancient kingdom of Champa and now living mainly in Vietnam and Cambodia, with distinct Islamic traditions and cultural practices.
  • C. Chamavi
    The Chamavi were an early Germanic tribe, likely part of the broader West Germanic group, known from Roman-era sources in the region of the lower Rhine.
  • D. Chamalal
    Chamalal is a Northeast Caucasian language spoken by the Chamalal people in the western part of Dagestan, Russia.
  • E. Chambarak
    Chambarak is a town in eastern Armenia known for its location in the mountainous Gegharkunik region near Lake Sevan.
  • 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_69d8b90916008190a1f110bd7ced5473 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4ddd58ea8819081e2bec5e591e093 completed April 19, 2026, 1:51 p.m.
Created at: April 10, 2026, 10:28 a.m.