Triple
T31544277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Irish Rifles |
E804829
|
entity |
| Predicate | dateRegimentalTitleChanged |
P171952
|
FINISHED |
| Object | 1921 |
—
|
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: 1921 | Statement: [Royal Irish Rifles, dateRegimentalTitleChanged, 1921]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRegimentalTitleChanged Context triple: [Royal Irish Rifles, dateRegimentalTitleChanged, 1921]
-
A.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
-
B.
regimentalTitleAbbreviation
Indicates the abbreviated form of a regiment’s official title used to represent that regiment in shortened or symbolic notation.
-
C.
regimentalColonelTitle
Indicates that a person holds the rank or title of colonel within a specific regiment.
-
D.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
E.
hasRegimentalNickname
Indicates that a military regiment is associated with a specific informal or traditional nickname.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:07 p.m.