Triple

T7345063
Position Surface form Disambiguated ID Type / Status
Subject Pancana language E169355 entity
Predicate hasGlottologName P6521 FINISHED
Object Pancana E658285 NE FINISHED

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: Pancana | Statement: [Pancana language, hasGlottologName, Pancana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pancana
Context triple: [Pancana language, hasGlottologName, Pancana]
  • A. Pancana chosen
    Pancana is an Austronesian language spoken by the Pancana people of Sulawesi, Indonesia.
  • B. Panchai Palang
    Panchai Palang is the alternative name for Operation Panther’s Claw, a major British-led military offensive conducted in Afghanistan during the War in Afghanistan.
  • C. Payangan
    Payangan is a rural district in central Bali, Indonesia, known for its terraced rice fields, river valleys, and traditional Balinese villages.
  • D. Pakpak Keppas
    Pakpak Keppas is a regional dialect of the Pakpak Dairi language spoken by the Pakpak ethnic community in parts of North Sumatra, Indonesia.
  • E. Bantia
    Bantia was an ancient Oscan-speaking city in southern Italy, notable for yielding important inscriptions that illuminate the Oscan language and Italic legal traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c68a57710481909f0c1f3c6ebdb6f2 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f0eeb30081909d25704ac9b49d0e completed March 27, 2026, 9:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802b24194819096b796de15d66ed2 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 3:05 p.m.