Triple
T1472115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mass of Paul VI |
E27157
|
entity |
| Predicate | centralAction |
P15354
|
FINISHED |
| Object | celebration of the Eucharist |
—
|
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: celebration of the Eucharist | Statement: [Mass of Paul VI, centralAction, celebration of the Eucharist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralAction Context triple: [Mass of Paul VI, centralAction, celebration of the Eucharist]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
C.
managedAct
Indicates that one entity oversaw, directed, or was responsible for carrying out a particular action or activity.
-
D.
hasCentralAct
chosen
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
-
E.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
- 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_69a496d25d6881909dbd84f86d763992 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c5dc90e481908a4935f266bc7850 |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48350d88190a81bd149103f93e3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:01 p.m.