Triple
T22440239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秋篠宮紀子妃 |
E554734
|
entity |
| Predicate | 皇位継承順位に関する立場 |
P74000
|
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.
皇位継承順位への関係
chosen
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.
-
B.
皇位継承資格の根拠
Indicates the basis or grounds on which a person is deemed eligible to inherit the imperial throne.
-
C.
positionInLineOfSuccessionToThrone
Indicates the ordinal place an individual holds in the ordered sequence of heirs eligible to inherit a throne.
-
D.
isNextInLineOfSuccessionTo
Indicates that one entity is the immediate heir or successor designated to take over a position, title, or role when the current holder can no longer occupy it.
-
E.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae0edcc8190919b198035de0df2 |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.