Triple
T22440253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秋篠宮紀子妃 |
E554734
|
entity |
| Predicate | 夫の地位 |
P148199
|
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.
notableDaimyo
Indicates that a person held the status of a daimyō and is recognized as particularly prominent or historically significant among daimyō.
-
B.
義理の息子
Indicates a relationship where someone is another person's son-in-law or stepson, i.e., a son by marriage or through a non-biological parental tie.
-
C.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
-
D.
firstDaimyo
Indicates that the subject is the first (initial or founding) daimyō associated with the specified domain, lineage, or context.
-
E.
heirOf
Indicates that one entity is the legal or designated successor who inherits from another entity, typically upon that entity’s death or transfer of rights.
- 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_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. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.