Triple
T32384708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chunjie |
E827516
|
entity |
| Predicate | preparatoryDay |
P174011
|
FINISHED |
| Object | Chinese New Year’s Eve |
—
|
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: Chinese New Year’s Eve | Statement: [Chunjie, preparatoryDay, Chinese New Year’s Eve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparatoryDay Context triple: [Chunjie, preparatoryDay, Chinese New Year’s Eve]
-
A.
preparationPeriod
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
B.
preparatoryFastBegins
Indicates that a required period of fasting starts in preparation for a subsequent event, action, or ritual.
-
C.
preparesFor
Indicates that one entity is used, designed, or undertaken in order to get another entity ready for a future event, state, or activity.
-
D.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
E.
preparatoryRole
Indicates that one entity performs a function or activity that serves as preparation or groundwork for another entity, event, or process.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1cf2aa081909f4c0b8f0cad1907 |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:51 a.m.