Triple

T17100644
Position Surface form Disambiguated ID Type / Status
Subject Panjalu E414970 entity
Predicate hasRuler P5424 FINISHED
Object Kameçvara E104718 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: Kameçvara | Statement: [Panjalu, hasRuler, Kameçvara]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kameçvara
Context triple: [Panjalu, hasRuler, Kameçvara]
  • A. Kameçvara chosen
    Kameçvara was a prominent king of the medieval Javanese Kediri Kingdom, remembered for his prosperous reign and association with the classic romance tale of Panji.
  • B. Kamenjar
    Kamenjar is a small settlement within the municipality of Temerin in the Vojvodina region of northern Serbia.
  • C. Kopaska
    Kopaska is the Indonesian Navy’s elite frogman and special operations unit, specializing in underwater demolition, maritime sabotage, and counter-terrorism missions.
  • D. Kamëz
    Kamëz is a suburban municipality and rapidly growing town in central Albania, situated just northwest of the capital city, Tirana.
  • E. Karesi
    Karesi is a central district and municipality of Balıkesir in western Turkey, known for its role as an administrative and commercial hub of the province.
  • 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_69d886cfc8e88190b05ba466edd35591 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dc0182cc8190b8aa9c980f11ba57 completed April 18, 2026, 7:31 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0141422d6c819086dc98988c0851d9 completed May 11, 2026, 2:38 a.m.
Created at: April 10, 2026, 5:35 a.m.