Triple
T305141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reiwa |
E6280
|
entity |
| Predicate | occasionForStart |
P10624
|
FINISHED |
| Object | accession of Emperor Naruhito |
—
|
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: accession of Emperor Naruhito | Statement: [Reiwa, occasionForStart, accession of Emperor Naruhito]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occasionForStart Context triple: [Reiwa, occasionForStart, accession of Emperor Naruhito]
-
A.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
B.
announcementOccasion
Indicates the specific event, context, or circumstance on the basis of which an announcement is made.
-
C.
displayOccasion
Indicates the event, context, or situation during which something is presented, shown, or made visible.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
- 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.