Triple
T191452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transfiguration |
E3730
|
entity |
| Predicate | dateInRomanCatholicChurch |
P7861
|
FINISHED |
| Object | 6 August |
—
|
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: 6 August | Statement: [Transfiguration, dateInRomanCatholicChurch, 6 August]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInRomanCatholicChurch Context triple: [Transfiguration, dateInRomanCatholicChurch, 6 August]
-
A.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
B.
canonizationDate
Indicates the date on which an individual was officially declared a saint (canonized) by a religious authority.
-
C.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
D.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_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_69a25673ce3c8190b1a3df5b814a0595 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a258fbd18881908c9d40f7a2480945 |
completed | Feb. 28, 2026, 2:54 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.