Triple
T25603884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen's Own Highlanders (Seaforth and Camerons) |
E641856
|
entity |
| Predicate | regimentalGroup |
P158904
|
FINISHED |
| Object | Highland Brigade |
—
|
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: Highland Brigade | Statement: [Queen's Own Highlanders (Seaforth and Camerons), regimentalGroup, Highland Brigade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalGroup Context triple: [Queen's Own Highlanders (Seaforth and Camerons), regimentalGroup, Highland Brigade]
-
A.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
battleGroup
Indicates that multiple military units or forces are organized together as a single coordinated combat formation.
-
C.
higherRegimentalUnit
Indicates that one military unit is hierarchically subordinate to another, which serves as its higher-level regimental command.
-
D.
guardRegiment
Indicates that one entity serves as a protective or security regiment for another entity.
-
E.
regimentalBand
Indicates that an entity serves as the official military band associated with a particular 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a89830819083b11f0b818e538d |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 4:37 p.m.