Triple
T31750431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadya Sheveleva |
E810399
|
entity |
| Predicate | celebratedHolidayInStory |
P84580
|
FINISHED |
| Object | New Year |
—
|
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: New Year | Statement: [Nadya Sheveleva, celebratedHolidayInStory, New Year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: celebratedHolidayInStory Context triple: [Nadya Sheveleva, celebratedHolidayInStory, New Year]
-
A.
celebratedDay
chosen
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
B.
celebratedDuring
Indicates that an event, tradition, or activity takes place or is observed within the time span of a specified celebration or festive period.
-
C.
isCelebratedAs
Indicates that an entity is recognized, honored, or regarded in a particular role, status, or capacity.
-
D.
isCelebrated
Indicates that a person, event, or occasion is honored, commemorated, or festively observed by others.
-
E.
celebrationDayDescription
Indicates a textual description that explains the nature, purpose, or significance of a particular celebration day.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab5262c88190bc54527b57ec2a81 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:27 p.m.