Triple
T1334861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrysanthemum Throne |
E28723
|
entity |
| Predicate | hasCoronationRitual |
P27876
|
FINISHED |
| Object | sokui no rei |
—
|
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: sokui no rei | Statement: [Chrysanthemum Throne, hasCoronationRitual, sokui no rei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoronationRitual Context triple: [Chrysanthemum Throne, hasCoronationRitual, sokui no rei]
-
A.
wasCrowned
Indicates that an entity formally received a crown or royal title in a ceremonial act of investiture.
-
B.
coronationStatus
Indicates the current stage or condition of an entity’s coronation process, such as whether it is pending, ongoing, or completed.
-
C.
firstCoronationHeld
Indicates that the referenced coronation event is the earliest (first in time) coronation associated with the given entity.
-
D.
coronationDate
Indicates the date on which an individual is formally crowned or installed into a royal or equivalent sovereign position.
-
E.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1eb119881909dd5fbf728d9e8ba |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4bef174708190a07bbc697fe19a2d |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c1bf31988190a659f48fe018f4bc |
completed | March 1, 2026, 10:46 p.m. |
Created at: March 1, 2026, 7:55 p.m.