Triple
T22440295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 眞子内親王 |
E554735
|
entity |
| Predicate | 身分変化 |
P117413
|
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 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.
-
B.
身分
Indicates a relationship where an entity holds a particular social, legal, or role-based status or identity in relation to a group, institution, or context.
-
C.
characterRoleSwap
Indicates a relationship where two characters exchange or assume each other’s narrative roles or functions within a story or scenario.
-
D.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
E.
bodyTransformedInto
Indicates that one entity’s physical form is changed or converted into another specified form or entity.
- 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.