Triple
T20778669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnostic Mass |
E511419
|
entity |
| Predicate | hasCommunion |
P141500
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gnostic Mass, hasCommunion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommunion Context triple: [Gnostic Mass, hasCommunion, yes]
-
A.
communionWith
Indicates a close, often spiritual or deeply intimate sharing or union between entities, characterized by mutual presence, participation, or fellowship.
-
B.
communionSince
Indicates that a state of communion, fellowship, or shared participation between entities has been in effect continuously since a specified point in time.
-
C.
communion
Indicates a close, often spiritual or emotional sharing or union between entities.
-
D.
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.
-
E.
partOfCommunion
Indicates that an entity participates in or belongs to a specific communion, such as a religious or sacramental union.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26ed1a08190bb73824672328d98 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:37 p.m.