Triple
T12390311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek Catholics |
E295975
|
entity |
| Predicate | usesLiturgicalChant |
P88276
|
FINISHED |
| Object | Byzantine chant |
—
|
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: Byzantine chant | Statement: [Greek Catholics, usesLiturgicalChant, Byzantine chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLiturgicalChant Context triple: [Greek Catholics, usesLiturgicalChant, Byzantine chant]
-
A.
usesLiturgicalMelody
chosen
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
-
B.
hasLiturgicalTone
Indicates that something (such as a chant, text, or musical phrase) is associated with or performed in a specific liturgical tone or mode.
-
C.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
D.
usesAlsoLiturgy
Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
-
E.
includesLiturgicalUse
Indicates that something encompasses or involves use within a liturgical or formal religious worship context.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd0bcc48190bb1a59a3aaa6bfdf |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:54 p.m.