Triple
T5305106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dum Spiro Spero |
E120081
|
entity |
| Predicate | hasMottoStatusIn |
P56183
|
FINISHED |
| Object | U.S. state mottos |
—
|
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: U.S. state mottos | Statement: [Dum Spiro Spero, hasMottoStatusIn, U.S. state mottos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMottoStatusIn Context triple: [Dum Spiro Spero, hasMottoStatusIn, U.S. state mottos]
-
A.
mottoStatus
Indicates the current state or classification of a motto, such as whether it is official, proposed, historical, or otherwise designated.
-
B.
hasMottoContext
chosen
Indicates that an entity’s motto is associated with or applies within a specific contextual setting or scope.
-
C.
hasMottoLikeFunction
Indicates that something serves a role or function similar to a motto, typically expressing a guiding principle, slogan, or core message.
-
D.
hasMottoInText
Indicates that an entity has a motto expressed in a specific textual form or wording.
-
E.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8e44e7c881909b241b2fec366038 |
completed | March 20, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69bd845097ac81909678624c4907fda4 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.