Triple
T2161182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regina Rifle Regiment |
E46803
|
entity |
| Predicate | honoraryColonel |
P34642
|
FINISHED |
| Object | appointed from local community leaders |
—
|
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: appointed from local community leaders | Statement: [Regina Rifle Regiment, honoraryColonel, appointed from local community leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoraryColonel Context triple: [Regina Rifle Regiment, honoraryColonel, appointed from local community leaders]
-
A.
colonelInChief
Indicates that one entity holds the ceremonial or honorary position of colonel-in-chief over a particular military unit or regiment.
-
B.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
C.
honoursPosition
chosen
Indicates that one entity holds or is recognized with an honorary or distinguished position in relation to another entity.
-
D.
hasColonelInChief
Indicates that an organization or military unit has a designated ceremonial leader holding the title of Colonel-in-Chief.
-
E.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe89e6ac8190b4b4bc0be4fe7aa9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.