Triple
T775443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 6 of the Constitution of Japan |
E16376
|
entity |
| Predicate | constitutionalStatusOfEmperor |
P10296
|
FINISHED |
| Object | symbolic head of state |
—
|
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: symbolic head of state | Statement: [Article 6 of the Constitution of Japan, constitutionalStatusOfEmperor, symbolic head of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalStatusOfEmperor Context triple: [Article 6 of the Constitution of Japan, constitutionalStatusOfEmperor, symbolic head of state]
-
A.
legalStatusOfMonarch
chosen
Indicates the legal status or standing that a monarch holds within a given legal or constitutional framework.
-
B.
definedEmperorAs
Indicates that one entity establishes or specifies another entity as holding the role or status of emperor.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
firstRecordedEmperorStatus
Indicates that the subject is recognized as the earliest historically recorded individual to hold the status or title of emperor.
-
E.
emperorTitle
Indicates that one entity holds the title or rank of emperor in relation to 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.