Triple
T13671198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festum Sanctorum Innocentium |
E327751
|
entity |
| Predicate | dateInSomeSpanishTraditions |
P7822
|
FINISHED |
| Object | 28 December |
—
|
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: 28 December | Statement: [Festum Sanctorum Innocentium, dateInSomeSpanishTraditions, 28 December]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInSomeSpanishTraditions Context triple: [Festum Sanctorum Innocentium, dateInSomeSpanishTraditions, 28 December]
-
A.
seCelebraEn
Indicates that an event or occasion takes place or is held at a specific location or venue.
-
B.
isMovableFeast
Indicates that an event or celebration occurs on a date that changes from year to year rather than being fixed on the calendar.
-
C.
isCelebratedIn
chosen
Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
-
D.
calendarTradition
Indicates a relationship where a calendar is based on, follows, or embodies a particular cultural, religious, or historical tradition.
-
E.
specialDaysName
Indicates that a special or notable day is identified or labeled with a particular name.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6599c248190b7f134b5b9947a23 |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.