Triple
T436498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armenian Rite |
E10020
|
entity |
| Predicate | communionPractice |
P9171
|
FINISHED |
| Object | communion under both kinds |
—
|
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: communion under both kinds | Statement: [Armenian Rite, communionPractice, communion under both kinds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communionPractice Context triple: [Armenian Rite, communionPractice, communion under both kinds]
-
A.
communion
Indicates a close, often spiritual or emotional sharing or union between entities.
-
B.
communionMode
chosen
Indicates the manner or form in which communion (a shared religious or spiritual rite) is practiced or administered between participants.
-
C.
communionWith
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
D.
sacramentAtServiceOfCommunion
Indicates that a sacrament is oriented toward and serves the purpose of fostering communion or unity among believers.
-
E.
communionPosture
Indicates the physical or bodily stance a person adopts while participating in communion.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef0c97188190b62104cb639d4b60 |
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.