Triple

T16917499
Position Surface form Disambiguated ID Type / Status
Subject Alexandra, Princess of Wales’s Own Yorkshire Regiment E410356 entity
Predicate hasRegimentalType P56207 FINISHED
Object line infantry LITERAL 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: line infantry | Statement: [Alexandra, Princess of Wales’s Own Yorkshire Regiment, hasRegimentalType, line infantry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegimentalType
Context triple: [Alexandra, Princess of Wales’s Own Yorkshire Regiment, hasRegimentalType, line infantry]
  • A. hasRegimentalIdentity
    Indicates that an entity possesses or is associated with a specific regimental identity, such as belonging to or being characterized by a particular regiment.
  • B. hasBattalionType
    Indicates that an entity (such as a military unit) is associated with or classified by a specific type of battalion.
  • C. regimentalCategory chosen
    Indicates the classification or type of regiment to which a military unit or formation belongs.
  • D. hasRegimentalNickname
    Indicates that a military regiment is associated with a specific informal or traditional nickname.
  • E. hasMilitaryType
    Indicates that an entity is associated with or classified under a specific military category, role, or type.
  • F. None of above.

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_69d886c7b1e481908c3766dfa8c13458 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3cdeb74c08190b6f247cdf4b21405 completed April 18, 2026, 6:31 p.m.
PD Predicate disambiguation batch_69e32b9489408190bcb2ede567ff5bf9 completed April 18, 2026, 6:58 a.m.
Created at: April 10, 2026, 5:30 a.m.