Triple
T35911929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oharai |
E1038638
|
entity |
| Predicate | performedForOccasion |
P56481
|
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: [Oharai, performedForOccasion, New Year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedForOccasion Context triple: [Oharai, performedForOccasion, New Year]
-
A.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
-
B.
suitableOccasion
Indicates that a particular occasion or context is appropriate or fitting for a given entity, action, or event.
-
C.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
-
D.
createdOnOccasionOf
chosen
Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
-
E.
onOccasionOf
Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:07 p.m.