Triple

T6195167
Position Surface form Disambiguated ID Type / Status
Subject Battle of Maloyaroslavets E138491 entity
Predicate location P40 FINISHED
Object Maloyaroslavets E509982 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: Maloyaroslavets | Statement: [Battle of Maloyaroslavets, location, Maloyaroslavets]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maloyaroslavets
Context triple: [Battle of Maloyaroslavets, location, Maloyaroslavets]
  • A. Maloyaroslavets chosen
    Maloyaroslavets is a historic town in western Russia known for the 1812 Battle of Maloyaroslavets during Napoleon’s invasion.
  • B. Zolotonosha
    Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
  • C. Luzhitsy
    Luzhitsy is a rural village in northwestern Russia historically associated with the Votic people and their traditional language and culture.
  • D. Oreshek
    Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
  • E. Pestovo
    Pestovo is a small town in northwestern Russia, situated within Novgorod Oblast and known as a local administrative and industrial center.
  • 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_69c008ab9b3081908a11b2c744838435 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c062443cec81909dc9bafea2f5e7d4 completed March 22, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69c243da922c819080d8d37adbb5635e completed March 24, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:19 p.m.