Triple
T31544305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Irish Rifles |
E804829
|
entity |
| Predicate | regimentalBadgeFeature |
P172575
|
FINISHED |
| Object | harp and crown |
—
|
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: harp and crown | Statement: [Royal Irish Rifles, regimentalBadgeFeature, harp and crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalBadgeFeature Context triple: [Royal Irish Rifles, regimentalBadgeFeature, harp and crown]
-
A.
regimentalColourSymbol
Indicates that something serves as the symbolic emblem or design used on a regiment’s official flag or standard.
-
B.
coatOfArmsFeatures
Indicates that a coat of arms includes or displays specific symbols, colors, or design elements as part of its heraldic composition.
-
C.
heraldicDivision
Indicates the way a heraldic shield or field is partitioned into distinct sections or areas.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
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. 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_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 10:07 p.m.