Triple
T29598292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geʻez era |
E754365
|
entity |
| Predicate | usedInLiturgicalBooks |
P13040
|
FINISHED |
| Object | Synaxarium (Ethiopian Orthodox) |
—
|
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: Synaxarium (Ethiopian Orthodox) | Statement: [Geʻez era, usedInLiturgicalBooks, Synaxarium (Ethiopian Orthodox)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInLiturgicalBooks Context triple: [Geʻez era, usedInLiturgicalBooks, Synaxarium (Ethiopian Orthodox)]
-
A.
usedInLiturgy
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
B.
includesLiturgicalUse
chosen
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
-
C.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
D.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
E.
hasLiturgicalMention
Indicates that one entity is referenced or mentioned within the liturgical texts, practices, or rites associated with 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: April 28, 2026, 6:20 p.m.