Triple
T31202487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Gloucestershire, Berkshire and Wiltshire Light Infantry |
E795510
|
entity |
| Predicate | mottoInheritedFromPredecessor |
P30365
|
FINISHED |
| Object | Firm |
—
|
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: Firm | Statement: [Royal Gloucestershire, Berkshire and Wiltshire Light Infantry, mottoInheritedFromPredecessor, Firm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoInheritedFromPredecessor Context triple: [Royal Gloucestershire, Berkshire and Wiltshire Light Infantry, mottoInheritedFromPredecessor, Firm]
-
A.
formerMotto
Indicates that a motto was previously used by an entity but is no longer its current motto.
-
B.
mottoDerivedFrom
chosen
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase associated with another entity.
-
E.
motto
Indicates that one entity serves as the guiding phrase, slogan, or maxim associated with another entity.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:09 p.m.