Triple
T14604343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1812 Caracas earthquake |
E342787
|
entity |
| Predicate | religiousCalendarDay |
P84580
|
FINISHED |
| Object | Holy Thursday |
—
|
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: Holy Thursday | Statement: [1812 Caracas earthquake, religiousCalendarDay, Holy Thursday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousCalendarDay Context triple: [1812 Caracas earthquake, religiousCalendarDay, Holy Thursday]
-
A.
religiousCalendar
Indicates that there is an association between an entity and a system of dates and observances defined by a particular religion or religious tradition.
-
B.
religiousCalendarRole
Indicates a role or function that something or someone has within a religious calendar, such as marking, organizing, or defining religious dates or observances.
-
C.
religiousHolidayCelebrated
Indicates that a particular religious holiday is observed or celebrated by an entity.
-
D.
ritualDate
Indicates the specific date on which a ritual or ceremonial event takes place.
-
E.
celebratedDay
chosen
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb44bf67c8190b4c48a7715f9443e |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.