Triple
T19094174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gloria Patri |
E467362
|
entity |
| Predicate | hasLatinName |
P3646
|
FINISHED |
| Object | Gloria Patri |
—
|
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: Gloria Patri | Statement: [Gloria Patri, hasLatinName, Gloria Patri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gloria Patri Context triple: [Gloria Patri, hasLatinName, Gloria Patri]
-
A.
Gloria Patri
chosen
Gloria Patri is a short Christian doxology traditionally used in liturgical prayer to give praise to the Holy Trinity.
-
B.
Sursum Corda
Sursum Corda is a Latin phrase meaning "Lift up your hearts," commonly used as a Christian liturgical exhortation and as an inspirational motto.
-
C.
Sursum Corda
Sursum Corda is a small residential neighborhood in Washington, D.C., known for its public housing roots and proximity to the city’s downtown.
-
D.
Gloria in excelsis Deo
"Gloria in excelsis Deo" is the jubilant opening chorus of Vivaldi’s Gloria in D major, RV 589, celebrating the glory of God in the highest.
-
E.
Gloria laus et honor
Gloria laus et honor is a medieval Latin hymn traditionally sung during Palm Sunday processions in the Christian liturgy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34e1ee0819092f679d916e6e532 |
completed | April 20, 2026, 8:26 a.m. |
Created at: April 10, 2026, 12:04 p.m.