Triple
T24288192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sei-i Taishōgun |
E605732
|
entity |
| Predicate | ceremonialSuperior |
P57327
|
FINISHED |
| Object | Emperor of Japan |
—
|
NE NERFINISHED |
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: Emperor of Japan | Statement: [Sei-i Taishōgun, ceremonialSuperior, Emperor of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialSuperior Context triple: [Sei-i Taishōgun, ceremonialSuperior, Emperor of Japan]
-
A.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
B.
ceremonialPowers
Indicates that an entity holds formal or symbolic authority associated with rituals or official ceremonies, without necessarily implying practical governing power.
-
C.
ceremonialStatus
Indicates the formal or symbolic standing an entity holds within a ritual, tradition, or official ceremony.
-
D.
ceremonialRoleInvolves
Indicates that a ceremonial role includes or entails performing a particular action, duty, or function as part of that ceremony.
-
E.
ceremonialHeadOffice
chosen
Indicates that an entity serves as the official but largely symbolic or ceremonial head office for another entity.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.