Triple
T9463553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Feast |
E228208
|
entity |
| Predicate | hasPreFestivePeriod |
P89087
|
FINISHED |
| Object | forefeast |
—
|
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: forefeast | Statement: [Great Feast, hasPreFestivePeriod, forefeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreFestivePeriod Context triple: [Great Feast, hasPreFestivePeriod, forefeast]
-
A.
hasFestivalPeriod
Indicates that there is a specific time period during which a festival or celebratory event takes place.
-
B.
occursBeforeMajorHoliday
Indicates that one event or time period happens earlier than a specified major holiday.
-
C.
hasCommonHoliday
Indicates that two entities share at least one holiday that is observed or celebrated in common.
-
D.
hasHolidayCycleStart
Indicates the point in time or event at which a recurring holiday cycle begins.
-
E.
hasFeastOrCommemoration
Indicates that a particular day, event, or context includes an associated religious feast, liturgical celebration, or commemorative observance.
- F. None of above. chosen
Provenance (4 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcec2d88190b93b6e4d881c85c6 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69ccbf9b080c819098934a18cf2bac5d |
completed | April 1, 2026, 6:47 a.m. |
Created at: March 30, 2026, 7:53 p.m.