Triple
T435314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christos |
E9797
|
entity |
| Predicate | hasLiturgicalUse |
P9871
|
FINISHED |
| Object | Christian worship |
—
|
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: Christian worship | Statement: [Christos, hasLiturgicalUse, Christian worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalUse Context triple: [Christos, hasLiturgicalUse, Christian worship]
-
A.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
-
B.
liturgicalUsage
Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
-
C.
usedInLiturgy
chosen
Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
-
D.
liturgicalUseApprovedBy
Indicates that the use of a liturgical text, rite, or practice has been formally authorized or approved by a specified authority.
-
E.
hasPrimaryLiturgicalForm
Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious practice.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef0b6e0c8190ad6a335ee804829c |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.