Triple
T19889039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of Saint Mary Magdalene |
E477979
|
entity |
| Predicate | elevatedToFeastOn |
P3787
|
FINISHED |
| Object | 3 June 2016 |
—
|
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: 3 June 2016 | Statement: [Feast of Saint Mary Magdalene, elevatedToFeastOn, 3 June 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToFeastOn Context triple: [Feast of Saint Mary Magdalene, elevatedToFeastOn, 3 June 2016]
-
A.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
B.
extendedFeast
Indicates a situation where a feast or celebratory meal continues for an unusually long or prolonged period of time.
-
C.
feastFollows
Indicates that a feast or celebratory meal occurs after and as a consequence of a preceding event or action.
-
D.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
E.
feastRelatedTo
Indicates a relationship in which one entity is connected or relevant to a feast, such as by association, participation, context, or thematic linkage.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590c1b9c8190abbfaa04b80713b3 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.