Triple
T10653013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Orders of South Africa |
E251018
|
entity |
| Predicate | mottoEmphasis |
P25715
|
FINISHED |
| Object | service, sacrifice and excellence |
—
|
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: service, sacrifice and excellence | Statement: [National Orders of South Africa, mottoEmphasis, service, sacrifice and excellence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoEmphasis Context triple: [National Orders of South Africa, mottoEmphasis, service, sacrifice and excellence]
-
A.
mottoEmphasizes
chosen
Indicates that a motto highlights, stresses, or gives special importance to a particular idea, value, or theme.
-
B.
mottoStyle
Indicates the stylistic form or presentation in which a motto is expressed.
-
C.
mottoPromoted
Indicates that a particular motto is actively advocated, endorsed, or publicized by an entity.
-
D.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff78ec88190a4d1863fe87245f6 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.