Triple
T15725827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese traditional calendar |
E381214
|
entity |
| Predicate | introducedGregorianCalendarInJapan |
P51800
|
FINISHED |
| Object | 1873 |
—
|
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: 1873 | Statement: [Japanese traditional calendar, introducedGregorianCalendarInJapan, 1873]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedGregorianCalendarInJapan Context triple: [Japanese traditional calendar, introducedGregorianCalendarInJapan, 1873]
-
A.
dateOfIntroductionToJapan
chosen
Indicates the date on which something was first introduced or brought into Japan.
-
B.
introducedToJapan
Indicates that one entity brought or presented another entity into Japan for the first time or for initial exposure there.
-
C.
modernDateInJapan
Indicates that a given date is interpreted or valid within the context of Japan’s modern calendar system (post–calendar reforms).
-
D.
traditionalDateInJapan
Indicates that an entity has a specific date expressed in the traditional Japanese calendar system (e.g., era-based or lunisolar date).
-
E.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
- 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_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. |
Created at: April 10, 2026, 4:46 a.m.