Triple
T35228740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift and Certain |
E1017169
|
entity |
| Predicate | isTranslationOfMottoMeaning |
P1683
|
FINISHED |
| Object | Certa Cito |
—
|
NE NERFINISHED |
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: Certa Cito | Statement: [Swift and Certain, isTranslationOfMottoMeaning, Certa Cito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTranslationOfMottoMeaning Context triple: [Swift and Certain, isTranslationOfMottoMeaning, Certa Cito]
-
A.
translationOfMotto
chosen
Indicates that one motto is a translation of another motto in a different language.
-
B.
reverseMottoTranslation
Indicates that one entity is a translation of another entity’s motto, rendered in the reverse language direction (from the target language back to the source language).
-
C.
mottoTransliteration
Indicates the representation of a motto’s original text using the characters of another writing system (its transliteration).
-
D.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
-
E.
hasTranslatedMeaning
Indicates that one entity expresses the meaning of another entity in a different language through translation.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.