Triple
T22073620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloria in excelsis Deo |
E545469
|
entity |
| Predicate | textOpeningTranslationEnglish |
P25592
|
FINISHED |
| Object | Glory to God in the highest |
—
|
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: Glory to God in the highest | Statement: [Gloria in excelsis Deo, textOpeningTranslationEnglish, Glory to God in the highest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textOpeningTranslationEnglish Context triple: [Gloria in excelsis Deo, textOpeningTranslationEnglish, Glory to God in the highest]
-
A.
textOpeningTranslation
Indicates that a text serves as a translation of the opening section of another text.
-
B.
translationOfOpeningWords
chosen
Indicates that one text is a translation of the initial words or opening phrase of another text.
-
C.
openingVerseTranslation
Indicates the specific translated rendering of the opening verse of a text or work.
-
D.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
E.
textTranslation
Indicates a relationship where one text is rendered into another language or form while preserving its original meaning.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12889f504819089830202e64d97b0 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.