Triple

T11972922
Position Surface form Disambiguated ID Type / Status
Subject Battle of Muktsar E284964 entity
Predicate locatedIn P40 FINISHED
Object Muktsar E304504 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: Muktsar | Statement: [Battle of Muktsar, locatedIn, Muktsar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muktsar
Context triple: [Battle of Muktsar, locatedIn, Muktsar]
  • A. Muktsar chosen
    Muktsar is a historic town in Punjab, India, known for its association with Sikh history and the Battle of Muktsar fought in 1705.
  • B. Baghmara
    Baghmara is a town in the South Garo Hills district of Meghalaya, India, known as a gateway to nearby forests, caves, and wildlife areas.
  • C. Firozkoh
    Firozkoh was the medieval royal city and cultural center of the Ghurid dynasty in present-day central Afghanistan, renowned for its architectural and artistic achievements before its destruction by the Mongols.
  • D. Keraniganj
    Keraniganj is a suburban upazila of Dhaka, Bangladesh, known for its dense population, river-based commerce, and numerous garment and brick industries.
  • E. Khandbari
    Khandbari is a hill town in eastern Nepal that serves as an administrative, commercial, and transportation hub for the surrounding mountainous region.
  • 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_69d6ab2eaeb881909f7914758f859413 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9039107e48190ae4c4efd6257dd3c completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f49d0791348190a2f6c0e808af3aea completed May 1, 2026, 12:31 p.m.
Created at: April 8, 2026, 9:46 p.m.