Triple

T37328601
Position Surface form Disambiguated ID Type / Status
Subject 45th (Nottinghamshire) Regiment of Foot E926676 entity
Predicate regimentalSystemReform P187983 FINISHED
Object Cardwell Reforms 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: Cardwell Reforms | Statement: [45th (Nottinghamshire) Regiment of Foot, regimentalSystemReform, Cardwell Reforms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regimentalSystemReform
Context triple: [45th (Nottinghamshire) Regiment of Foot, regimentalSystemReform, Cardwell Reforms]
  • A. regimentalTitleChangedTo
    Indicates that a military regiment’s official title has been changed from one specific designation to another.
  • B. regimentalCategory
    Indicates the classification or type of regiment to which a military unit or formation belongs.
  • C. upgradedToRegiment
    Indicates that a military unit or formation has been elevated in status, size, or organizational level to become a regiment.
  • D. militarySystem
    Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
  • E. raisedRegiment
    Indicates that an entity organized, formed, or brought into existence a specific military regiment.
  • F. None of above. chosen

Provenance (4 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_69f76eb386d88190a8d511aa11540dfc completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb9e1845e881908d19158440cf3b87 completed May 6, 2026, 8:01 p.m.
PD Predicate disambiguation batch_69fb8d08d6988190a00794ac26078348 completed May 6, 2026, 6:48 p.m.
PDg Predicate description generation batch_69fb9e173f348190b7ab5935e4dca039 completed May 6, 2026, 8:01 p.m.
Created at: May 3, 2026, 4:16 p.m.