Triple

T3614177
Position Surface form Disambiguated ID Type / Status
Subject Sikh people E76559 entity
Predicate observes P134 FINISHED
Object Maghi E114662 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: Maghi | Statement: [Sikh people, observes, Maghi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maghi
Context triple: [Sikh people, observes, Maghi]
  • A. Maghi chosen
    Maghi is a regional name for the Hindu harvest festival of Makar Sankranti, particularly observed in parts of North India.
  • B. Dhulandi
    Dhulandi is the vibrant second day of the Holi festival in India, celebrated with the playful throwing of colored powders and water.
  • C. Murzuq
    Murzuq is an oasis town in southwestern Libya that historically served as an important Saharan trade and caravan center in the Fezzan region.
  • D. Shuja
    Shuja is a given name most notably associated with Shuja Shah Durrani, a 19th-century ruler of the Durrani Empire in Afghanistan.
  • E. Mutasa
    Mutasa is a town located in Zimbabwe’s eastern Manicaland Province, known for its rural communities and proximity to the Eastern Highlands.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc279f6948190b9655a4cf3e77d89 completed March 8, 2026, 6:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69b43316224081909372f1007becc663 completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:23 p.m.