Triple
T14841937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Battalion Scots Guards |
E348984
|
entity |
| Predicate | hasRegimentalMotto |
P20052
|
FINISHED |
| Object | Nemo me impune lacessit |
—
|
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: Nemo me impune lacessit | Statement: [2nd Battalion Scots Guards, hasRegimentalMotto, Nemo me impune lacessit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegimentalMotto Context triple: [2nd Battalion Scots Guards, hasRegimentalMotto, Nemo me impune lacessit]
-
A.
hasRegimentalNickname
Indicates that a military regiment is associated with a specific informal or traditional nickname.
-
B.
mottoOfBranch
Indicates that a particular motto is officially associated with and represents a specific branch of an organization or institution.
-
C.
isMottoOf
chosen
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded28fa49c81908d1059e6cafd607f |
completed | April 14, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:53 a.m.