Triple
T305163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiwa |
E6280
|
entity |
| Predicate | eraNumber |
P2938
|
FINISHED |
| Object | current era in the modern sequence Shōwa–Heisei–Reiwa |
—
|
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: current era in the modern sequence Shōwa–Heisei–Reiwa | Statement: [Reiwa, eraNumber, current era in the modern sequence Shōwa–Heisei–Reiwa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraNumber Context triple: [Reiwa, eraNumber, current era in the modern sequence Shōwa–Heisei–Reiwa]
-
A.
eraName
chosen
Indicates the named historical or chronological era associated with an entity or time period.
-
B.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
C.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
D.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
E.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
- 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_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. |
Created at: Feb. 28, 2026, 1:06 p.m.