Triple
T9781858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syriac Churches |
E237393
|
entity |
| Predicate | hasLiturgicalMusic |
P88276
|
FINISHED |
| Object | Syriac 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: Syriac chant | Statement: [Syriac Churches, hasLiturgicalMusic, Syriac chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalMusic Context triple: [Syriac Churches, hasLiturgicalMusic, Syriac chant]
-
A.
usesLiturgicalMelody
chosen
Indicates that one entity employs or incorporates a specific liturgical melody in its music or performance.
-
B.
hasLiturgicalExpression
Indicates that one entity expresses, embodies, or is manifested through the liturgical practices, rites, or worship forms of another entity.
-
C.
hasLiturgicalStructure
Indicates that something possesses an established form or order of worship, ritual, or liturgical arrangement.
-
D.
hasLiturgicalNature
Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
-
E.
hasLiturgicalTexts
Indicates that an entity possesses or is associated with specific liturgical texts used in religious worship or ceremonies.
- 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_69ca84da927881909bda80caecad6010 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda1b23cb88190b458ab18d5f7f493 |
completed | April 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.