Triple
T32754852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geʽez language |
E837593
|
entity |
| Predicate | hasLiturgyName |
P9515
|
FINISHED |
| Object | Qeddase (Mass) in Geʽez |
—
|
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: Qeddase (Mass) in Geʽez | Statement: [Geʽez language, hasLiturgyName, Qeddase (Mass) in Geʽez]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgyName Context triple: [Geʽez language, hasLiturgyName, Qeddase (Mass) in Geʽez]
-
A.
hasLiturgicalName
chosen
Indicates that an entity is associated with a specific name used in liturgical or religious worship contexts.
-
B.
hasLiturgicalMention
Indicates that one entity is referenced or mentioned within the liturgical texts, practices, or rites associated with another entity.
-
C.
hasLiturgicalNature
Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
-
D.
hasLiturgicalSymbol
Indicates that one entity serves as a liturgical symbol or emblem associated with another entity within a religious or worship context.
-
E.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:12 a.m.