Triple
T22482409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 黒田清子 |
E555798
|
entity |
| Predicate | 皇族としての身位 |
P44258
|
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.
皇室典範による身分変化
Indicates a change in a person’s legal or social status that occurs specifically as a result of provisions or decisions based on the Imperial House Law.
-
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.
monarchicalRole
Indicates that one entity holds or is assigned a specific position, function, or office within a monarchical system of governance.
-
E.
hasRoyalStatus
chosen
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3a3b688190b41599979d038d85 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.