Triple
T5905058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 悠仁親王 |
E131322
|
entity |
| Predicate | 皇位継承資格の根拠 |
P66842
|
FINISHED |
| Object | 皇室典範第1条・第2条 |
—
|
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: 皇室典範第1条・第2条 | Statement: [悠仁親王, 皇位継承資格の根拠, 皇室典範第1条・第2条]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 皇位継承資格の根拠 Context triple: [悠仁親王, 皇位継承資格の根拠, 皇室典範第1条・第2条]
-
A.
legalBasisForBritishSuccession
Indicates the legal foundation or authority that determines how succession to the British throne is established or regulated.
-
B.
dynasticClaimBasis
Indicates the basis or grounds on which a person or lineage asserts a dynastic right or claim to rule.
-
C.
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.
-
D.
dynasticPrinciple
Indicates that a relationship is governed by rules of hereditary succession or dynastic inheritance within a ruling family or lineage.
-
E.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03ee10b308190afe38b904ae7c5f7 |
completed | March 22, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69c0334fcf6481908e8e74105de9d49b |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03edf98b881908e9dbc03d3fd6218 |
completed | March 22, 2026, 7:11 p.m. |
Created at: March 22, 2026, 3:59 p.m.