Triple
T25063026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 上皇后美智子 |
E627708
|
entity |
| Predicate | 系譜上の位置 |
P128953
|
FINISHED |
| Object | 日本で初めての純粋な民間出身の皇太子妃 |
—
|
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: 日本で初めての純粋な民間出身の皇太子妃 | Statement: [上皇后美智子, 系譜上の位置, 日本で初めての純粋な民間出身の皇太子妃]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 系譜上の位置 Context triple: [上皇后美智子, 系譜上の位置, 日本で初めての純粋な民間出身の皇太子妃]
-
A.
positionInFamilyTree
chosen
Indicates the familial relationship or generational position one person holds relative to another within a family tree.
-
B.
basedOnCharacterLineage
Indicates that one entity is derived from, inspired by, or determined according to the ancestral or familial lineage of a character.
-
C.
皇位継承順位への関係
Indicates the relationship of an entity to the line of succession to the imperial throne, such as its position, eligibility, or connection within that succession order.
-
D.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
E.
hasOrdinalInFamilyLine
Indicates that an entity holds a specific ordinal position (e.g., first, second, third) within a family lineage or sequence of family members.
- 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_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. |
Created at: April 18, 2026, 6:10 a.m.