Triple
T211583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tridentine Mass |
E4730
|
entity |
| Predicate | communionMode |
P9171
|
FINISHED |
| Object | on the tongue |
—
|
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: on the tongue | Statement: [Tridentine Mass, communionMode, on the tongue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communionMode Context triple: [Tridentine Mass, communionMode, on the tongue]
-
A.
communion
Indicates a close, often spiritual or emotional sharing or union between entities.
-
B.
communionWith
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
C.
hasInstrumentOfCommunion
Indicates that one entity uses or is associated with a specific instrument, medium, or means through which communion, connection, or shared participation with another entity is established or maintained.
-
D.
sacramentalUseOf
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
E.
recognizesSacrament
Indicates that one entity formally accepts or acknowledges the validity or legitimacy of a particular sacrament associated with another entity.
- F. None of above. chosen
Provenance (4 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25d35aa288190966b6e15af1525cb |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b4f71b88190866c8262922ae204 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25d3463648190ac716d7475378536 |
completed | Feb. 28, 2026, 3:12 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.