Triple
T25063007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 上皇后美智子 |
E627708
|
entity |
| Predicate | 在位期間_皇太子妃 |
P157591
|
FINISHED |
| Object | 1959-04-10/1989-01-07 |
—
|
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: 1959-04-10/1989-01-07 | Statement: [上皇后美智子, 在位期間_皇太子妃, 1959-04-10/1989-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在位期間_皇太子妃 Context triple: [上皇后美智子, 在位期間_皇太子妃, 1959-04-10/1989-01-07]
-
A.
monarchDuringReignAsEmpress
Indicates that the subject was the reigning monarch during the period in which she held the title of empress.
-
B.
heirApparentDuringReign
Indicates that one entity was officially recognized as the designated heir apparent to another entity’s position or title during the latter’s period of reign.
-
C.
endTimeOfPositionEmpressConsort
Indicates the point in time when an individual's tenure in the role of Empress Consort comes to an end.
-
D.
successorAsEmpress
Indicates that one person became the next empress following another, directly succeeding her in that imperial role.
-
E.
successorAsChiefImperialLady
Indicates that one person becomes the next holder of the position of Chief Imperial Lady after another person.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599b7ff081909862edeae57c2c2d |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:10 a.m.