Triple
T191471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfiguration |
E3730
|
entity |
| Predicate | liturgicalRankInRomanCatholicChurch |
P3655
|
FINISHED |
| Object | Feast |
—
|
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: Feast | Statement: [Transfiguration, liturgicalRankInRomanCatholicChurch, Feast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalRankInRomanCatholicChurch Context triple: [Transfiguration, liturgicalRankInRomanCatholicChurch, Feast]
-
A.
hasLiturgicalRank
chosen
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
C.
ordainedBy
Indicates that an entity has been formally appointed, consecrated, or invested with authority by another entity.
-
D.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
E.
religiousTitle
Indicates that one entity holds or is referred to by a specific religious rank, honorific, or clerical title in relation to 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25964fc5c8190bd3e37daaf695ecf |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.