Triple
T36899588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope John X |
E911992
|
entity |
| Predicate | supportedLiturgicalTraditions |
P1186
|
FINISHED |
| Object | Roman rite |
—
|
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: Roman rite | Statement: [Pope John X, supportedLiturgicalTraditions, Roman rite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedLiturgicalTraditions Context triple: [Pope John X, supportedLiturgicalTraditions, Roman rite]
-
A.
liturgicalTradition
Indicates the specific religious rite or ceremonial tradition according to which a worship service, practice, or community operates.
-
B.
hasRiteOrTradition
chosen
Indicates that an entity is associated with, practices, or observes a particular rite, ritual, or tradition.
-
C.
hasLiturgicalHeritage
Indicates that one entity possesses or is associated with the liturgical tradition, practices, or rites originating from another entity.
-
D.
hasLiturgicalChurch
Indicates that one entity is associated with, served by, or belongs to a particular liturgical church as its religious institution.
-
E.
worshipTradition
Indicates that one entity follows, practices, or is associated with a particular religious or spiritual worship tradition.
- 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.