Triple
T2257241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaudete Sunday |
E49754
|
entity |
| Predicate | scripturalMotto |
P36775
|
FINISHED |
| Object | "Rejoice in the Lord always" |
—
|
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: "Rejoice in the Lord always" | Statement: [Gaudete Sunday, scripturalMotto, "Rejoice in the Lord always"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalMotto Context triple: [Gaudete Sunday, scripturalMotto, "Rejoice in the Lord always"]
-
A.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
B.
mottoInterpretation
Indicates the explanatory relationship between a motto and its intended meaning or message.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
mottoType
Indicates the specific category or kind of motto that characterizes the relationship between an entity and its motto.
-
E.
mottoDerivedFrom
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
- F. None of above. chosen
Provenance (4 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_69a88aaa9250819095e127d0d77e8a32 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1570dc88190bb2b17ed4c25dbb5 |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbdb34c148190b51e99f540f97204 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe86dbcc81908c72793af8fe2a4d |
completed | March 7, 2026, 5:58 a.m. |
Created at: March 4, 2026, 7:47 p.m.