Triple
T20870885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinpūren |
E513887
|
entity |
| Predicate | viewedEmperorAs |
P142177
|
FINISHED |
| Object | divine figure |
—
|
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: divine figure | Statement: [Shinpūren, viewedEmperorAs, divine figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedEmperorAs Context triple: [Shinpūren, viewedEmperorAs, divine figure]
-
A.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
B.
emperorRole
Indicates that an entity holds or fulfills the role, position, or office of an emperor in relation to another entity or context.
-
C.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
-
D.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
E.
finalEmperorOf
Indicates that one entity is the last ruler to hold the imperial title over another entity (such as a state, dynasty, or empire).
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c4649cf88190b3ad946576aa46aa |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53c4d6881909b4d0a716fa5ed4a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:45 p.m.