Triple
T15725829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese traditional calendar |
E381214
|
entity |
| Predicate | usesSexagenaryCycleFor |
P119940
|
FINISHED |
| Object | days |
—
|
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: days | Statement: [Japanese traditional calendar, usesSexagenaryCycleFor, days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSexagenaryCycleFor Context triple: [Japanese traditional calendar, usesSexagenaryCycleFor, days]
-
A.
heavenlyStemsCycleLength
Indicates the length of the repeating cycle of the Heavenly Stems sequence in a calendrical or ordinal system.
-
B.
isLunisolar
Indicates that something is based on or determined by both the cycles of the moon and the sun.
-
C.
earthlyBranchesCycleLength
Indicates the length of the repeating cycle formed by the sequence of earthly branches in a given calendrical or symbolic system.
-
D.
usedInCalendarSystem
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
E.
doesNotUseLeapMonths
Indicates that the referenced calendar or timekeeping system does not incorporate leap months to adjust for discrepancies between its cycle and the astronomical year.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb357a88190a92641c8a8c20573 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0094af5b481908ad51d5d7ba0c726 |
completed | April 15, 2026, 9:55 p.m. |
Created at: April 10, 2026, 4:46 a.m.