Triple
T35478551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dormition Cathedral |
E1025403
|
entity |
| Predicate | dedicationFeast |
P152060
|
FINISHED |
| Object | Feast of the Dormition |
—
|
NE NERFINISHED |
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 of the Dormition | Statement: [Dormition Cathedral, dedicationFeast, Feast of the Dormition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicationFeast Context triple: [Dormition Cathedral, dedicationFeast, Feast of the Dormition]
-
A.
institutedFeast
Indicates that an authority or group formally established and put into practice a particular feast or festival as an ongoing observance.
-
B.
dedicationDay
Indicates the date or day on which something, typically a building, monument, or work, is formally dedicated or inaugurated.
-
C.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
D.
feastOf
chosen
Indicates that one entity is the religious or ceremonial feast day associated with another entity (such as a person, event, or deity).
-
E.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.