Triple
T2309629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Saint Barbara |
E51921
|
entity |
| Predicate | hasMottoOrTheme |
P29651
|
FINISHED |
| Object | recognition of excellence in artillery |
—
|
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: recognition of excellence in artillery | Statement: [Order of Saint Barbara, hasMottoOrTheme, recognition of excellence in artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoOrTheme Context triple: [Order of Saint Barbara, hasMottoOrTheme, recognition of excellence in artillery]
-
A.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
B.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
C.
usesMotto
chosen
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
D.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a motto.
-
E.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.