Triple

T10885240
Position Surface form Disambiguated ID Type / Status
Subject Battle of Mursa Major E257025 entity
Predicate location P40 FINISHED
Object Mursa E867179 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: Mursa | Statement: [Battle of Mursa Major, location, Mursa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mursa
Context triple: [Battle of Mursa Major, location, Mursa]
  • A. Mursa chosen
    Mursa was an important Roman city and military center located in the province of Pannonia, in the region of modern-day Osijek, Croatia.
  • B. Musasir
    Musasir was an ancient Urartian city and religious center in the Armenian Highlands, renowned for its prominent temple dedicated to the god Haldi.
  • C. Anazarbus
    Anazarbus was an important ancient city in the region of Cilicia, in what is now southern Turkey, known for its strategic location and impressive fortifications.
  • D. Gharsana
    Gharsana is a town in the arid northwestern region of Rajasthan, India, known for its agriculture supported by canal irrigation and its proximity to the India–Pakistan border.
  • E. Medraut
    Medraut is an alternative name for Mordred, the treacherous knight of Arthurian legend who fatally wounds King Arthur at Camlann.
  • 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_69d6aa848804819081b2713ca0bedf06 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d751dd6a3c81909965ef774e8b7309 completed April 9, 2026, 7:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69dff7ecf1c48190aef0d31ef03d1f88 completed April 15, 2026, 8:41 p.m.
Created at: April 8, 2026, 9:21 p.m.