Triple
T6896717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 佳子内親王 |
E159387
|
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.
皇位継承資格の根拠
Indicates the basis or grounds on which a person is deemed eligible to inherit the imperial throne.
-
B.
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.
-
C.
successionRelation
Indicates that one entity follows another in an ordered sequence, such as in time, position, or rank.
-
D.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
E.
constitutionalMonarchRelation
Indicates that one entity serves as a constitutional monarch in relation to another entity, over which they act as a ceremonial head of state within a constitutional framework.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.