Triple
T18019395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stronger, Fairer, Faster |
E431075
|
entity |
| Predicate | typeOfMotto |
P504
|
FINISHED |
| Object | organizational 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: organizational motto | Statement: [Stronger, Fairer, Faster, typeOfMotto, organizational motto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMotto Context triple: [Stronger, Fairer, Faster, typeOfMotto, organizational motto]
-
A.
mottoType
chosen
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
B.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
C.
definesMotto
Indicates that one entity establishes or specifies the official motto associated with another entity.
-
D.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
E.
honorificMotto
Indicates that one entity serves as an honorific motto or formal laudatory phrase 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c09fdc819097a7fa07d44b0505 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.