Triple

T38434833
Position Surface form Disambiguated ID Type / Status
Subject A Squadron E903910 entity
Predicate parentRegimentType P163001 FINISHED
Object armoured regiment 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: armoured regiment | Statement: [A Squadron, parentRegimentType, armoured regiment]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parentRegimentType
Context triple: [A Squadron, parentRegimentType, armoured regiment]
  • A. parentRegimentDesignation chosen
    Indicates that one military regiment is designated as the parent or higher-level regiment to which another regiment belongs or from which it is derived.
  • B. regimentalCategory
    Indicates the classification or type of regiment to which a military unit or formation belongs.
  • C. parentRegimentMotto
    Indicates that one regiment’s motto is derived from, associated with, or officially linked to the motto of its parent regiment.
  • D. regimentalFamily
    Indicates a familial or close-kin relationship that exists within, or is defined by, a shared regimental or military unit affiliation.
  • E. 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.
  • 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_69f76e6a2024819081aa04f4932f89d2 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fe91383a1c81909266e40c3c3ede6c completed May 9, 2026, 1:43 a.m.
PD Predicate disambiguation batch_69fe8fde094081908f0f121664fbb5c7 completed May 9, 2026, 1:37 a.m.
Created at: May 3, 2026, 4:31 p.m.