Triple
T22140846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Fifth Festival |
E547152
|
entity |
| Predicate | dateInLunarCalendar |
P75844
|
FINISHED |
| Object | 5th day of the 5th month |
—
|
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: 5th day of the 5th month | Statement: [Double Fifth Festival, dateInLunarCalendar, 5th day of the 5th month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInLunarCalendar Context triple: [Double Fifth Festival, dateInLunarCalendar, 5th day of the 5th month]
-
A.
lunarCalendar
Indicates that the referenced system, event, or date is defined, measured, or scheduled according to a calendar based on the phases or cycles of the Moon.
-
B.
festivalMonthLunarCalendar
chosen
Indicates that a festival occurs in a specified month according to the lunar calendar.
-
C.
isLunisolar
Indicates that something is based on or determined by both the cycles of the moon and the sun.
-
D.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
E.
dateInRomanCalendar
Indicates that a given date is expressed according to the conventions and structure of the ancient Roman calendar system.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129beb6c8819083be3b7479bc032f |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.