Triple

T20098624
Position Surface form Disambiguated ID Type / Status
Subject Battle of Jajau E496473 entity
Predicate location P40 FINISHED
Object Jajau 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: Jajau | Statement: [Battle of Jajau, location, Jajau]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jajau
Context triple: [Battle of Jajau, location, Jajau]
  • A. Jajau chosen
    Jajau is a locality in northern India historically noted as the place where the Mughal prince Azam Shah died.
  • B. Jajaghu
    Jajaghu is an alternative name for the Jago Temple, an ancient religious structure in Indonesia known for its historical and architectural significance.
  • C. Jaji
    Jaji is a Pashtun tribe associated with the Karlani tribal confederation, primarily found in eastern Afghanistan and parts of Pakistan.
  • D. Jajamen
    Jajamen is a regional noodle dish from Morioka, Japan, featuring thick wheat noodles typically served with a savory meat-miso sauce and various toppings.
  • E. Gelgel
    Gelgel is a historic village in Bali, Indonesia, known as a former royal capital and cultural center of the Klungkung kingdom.
  • 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6666e306c81909c0ef617e0f6fccf completed April 20, 2026, 5:46 p.m.
Created at: April 11, 2026, 11:25 p.m.