Triple
T9627947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diet of Japan |
E232517
|
entity |
| Predicate | emperorRole |
P89342
|
FINISHED |
| Object | ceremonial convocation of the Diet |
—
|
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: ceremonial convocation of the Diet | Statement: [Diet of Japan, emperorRole, ceremonial convocation of the Diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emperorRole Context triple: [Diet of Japan, emperorRole, ceremonial convocation of the Diet]
-
A.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
B.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
-
E.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:10 p.m.