Triple
T305162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiwa |
E6280
|
entity |
| Predicate | chronologicalPosition |
P10630
|
FINISHED |
| Object | era after Heisei in the Japanese calendar |
—
|
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: era after Heisei in the Japanese calendar | Statement: [Reiwa, chronologicalPosition, era after Heisei in the Japanese calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicalPosition Context triple: [Reiwa, chronologicalPosition, era after Heisei in the Japanese calendar]
-
A.
chronologicallyAfter
Indicates that one event or state occurs later in time than another.
-
B.
workChronologyPosition
Indicates the relative ordering or position of a work within a sequence of works, such as in a career, series, or catalog.
-
C.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
D.
chronostratigraphicRank
Indicates the hierarchical level or rank of a unit within the chronostratigraphic (time-stratigraphic) classification system.
-
E.
movementDate
Indicates the date on which a movement, transfer, or relocation event occurs.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea11c4908190a8723033bdf6f479 |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea07e3bc8190bae593b3264de211 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.