Triple
T32313285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sovereign of the Order of the Bath |
E825558
|
entity |
| Predicate | hasMottoOnInsignia |
P141177
|
FINISHED |
| Object | Tria juncta in uno (Order of the Bath motto) |
—
|
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: Tria juncta in uno (Order of the Bath motto) | Statement: [Sovereign of the Order of the Bath, hasMottoOnInsignia, Tria juncta in uno (Order of the Bath motto)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOnInsignia Context triple: [Sovereign of the Order of the Bath, hasMottoOnInsignia, Tria juncta in uno (Order of the Bath motto)]
-
A.
hasMottoDepiction
Indicates that something visually represents or depicts the motto associated with an entity.
-
B.
hasMottoSymbol
Indicates that an entity’s motto is represented or accompanied by a particular symbol.
-
C.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a motto.
-
D.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
E.
mottoIncluded
chosen
Indicates that a motto is present as part of, or associated with, the referenced 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 12:46 a.m.