Triple
T22402448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, The Rifles |
E553792
|
entity |
| Predicate | parentRegimentMotto |
P148026
|
FINISHED |
| Object | Swift and Bold |
—
|
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: Swift and Bold | Statement: [4th Battalion, The Rifles, parentRegimentMotto, Swift and Bold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentRegimentMotto Context triple: [4th Battalion, The Rifles, parentRegimentMotto, Swift and Bold]
-
A.
regimentalMottoTranslation
Indicates the translated wording or meaning of a regiment’s official motto in another language.
-
B.
regimentalFamily
Indicates a familial or close-kin relationship that exists within, or is defined by, a shared regimental or military unit affiliation.
-
C.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
D.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
-
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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b565c48190b0f6c19f17995b40 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:46 p.m.