Triple
T24094004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L’Ascension |
E596862
|
entity |
| Predicate | religiousFeastDepicted |
P44757
|
FINISHED |
| Object | Feast of the Ascension |
—
|
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 Ascension | Statement: [L’Ascension, religiousFeastDepicted, Feast of the Ascension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousFeastDepicted Context triple: [L’Ascension, religiousFeastDepicted, Feast of the Ascension]
-
A.
institutedFeast
Indicates that an authority or group formally established and put into practice a particular feast or festival as an ongoing observance.
-
B.
majorFeast
Indicates that an event or celebration is recognized as a major religious or cultural feast of high importance.
-
C.
religiousHolidayCelebrated
Indicates that a particular religious holiday is observed or celebrated by an entity.
-
D.
hasFeastOrCommemoration
chosen
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
-
E.
religiousEvent
Indicates that an event is related to religious practices, observances, or ceremonies.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2332b48190a711b2a0a304f3c2 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 10:58 p.m.