Triple
T2257217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaudete Sunday |
E49754
|
entity |
| Predicate | introitText |
P12432
|
FINISHED |
| Object | "Gaudete in Domino semper" |
—
|
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: "Gaudete in Domino semper" | Statement: [Gaudete Sunday, introitText, "Gaudete in Domino semper"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introitText Context triple: [Gaudete Sunday, introitText, "Gaudete in Domino semper"]
-
A.
refrainText
Indicates that a piece of text functions as the recurring refrain or repeated line within a larger work, such as a song or poem.
-
B.
openingVerseTheme
Indicates the primary idea or motif expressed in the opening verse of a text, song, or poem.
-
C.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
-
D.
liturgicalText
chosen
Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
-
E.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
- 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_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. |
Created at: March 4, 2026, 7:47 p.m.