Triple
T22440251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秋篠宮紀子妃 |
E554734
|
entity |
| Predicate | 婚姻により取得した身位 |
P21956
|
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.
marriageThroughWhichTitleHeld
chosen
Indicates that a noble or formal title is held by a person specifically by virtue of (i.e., as a result of) a particular marriage.
-
B.
spouseNobilityStatus
Indicates that the predicate specifies the nobility rank or noble status held by a person’s spouse.
-
C.
elevatedByMarriageTo
Indicates that one entity attains a higher social, legal, or status position as a direct result of marrying another entity.
-
D.
positionOnMarriage
Indicates a person's stance, opinion, or policy regarding the institution or practice of marriage.
-
E.
receivedAsWifeFrom
Indicates that one entity was given or transferred to another entity specifically in the role or status of a wife.
- 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.