Triple

T37328600
Position Surface form Disambiguated ID Type / Status
Subject 45th (Nottinghamshire) Regiment of Foot E926676 entity
Predicate regimentalDepotAfter1873 P187731 FINISHED
Object Derby 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: Derby | Statement: [45th (Nottinghamshire) Regiment of Foot, regimentalDepotAfter1873, Derby]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regimentalDepotAfter1873
Context triple: [45th (Nottinghamshire) Regiment of Foot, regimentalDepotAfter1873, Derby]
  • A. regimentCommemorated
    Indicates that a particular regiment is formally remembered or honored, typically through a memorial, ceremony, or commemorative designation.
  • B. regimentalCategory
    Indicates the classification or type of regiment to which a military unit or formation belongs.
  • C. parentRegimentFormationYear
    Indicates the year in which the parent regiment associated with an entity was originally formed.
  • D. regimentalTitleChangedTo
    Indicates that a military regiment’s official title has been changed from one specific designation to another.
  • E. regimentalCollect
    Indicates a relationship where items, resources, or data are gathered and organized in a regimented, structured, or systematically controlled manner.
  • 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_69fb78cbef988190b8f79d946b46e6b2 completed May 6, 2026, 5:22 p.m.
PD Predicate disambiguation batch_69fb5a9ac5a08190b24ef308963fc52b completed May 6, 2026, 3:13 p.m.
PDg Predicate description generation batch_69fb78c982ac8190846efe8f6209e5d1 completed May 6, 2026, 5:22 p.m.
Created at: May 3, 2026, 4:16 p.m.