Triple
T3720639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | traditional Chinese calendar |
E81628
|
entity |
| Predicate | usesEpoch |
P16736
|
FINISHED |
| Object | sexagenary cycle year count |
—
|
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: sexagenary cycle year count | Statement: [traditional Chinese calendar, usesEpoch, sexagenary cycle year count]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesEpoch Context triple: [traditional Chinese calendar, usesEpoch, sexagenary cycle year count]
-
A.
epochReference
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
B.
isEpochBoundaryFor
Indicates that something marks or defines the transition point between two distinct epochs for another entity.
-
C.
calendarEpoch
chosen
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
usesUTCOffset
Indicates that one entity applies or relies on the specified UTC time offset for timekeeping or timestamp interpretation.
-
E.
usedForCivilTimeIn
Indicates that something (typically a time scale or standard) is used as the basis for keeping official civil time within a specified region or jurisdiction.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca9b5ca8819094299fffc02606ce |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.