Triple
T25436853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatsuko Kawashima |
E637397
|
entity |
| Predicate | has descendant |
P63247
|
FINISHED |
| Object | Prince Hisahito of Akishino |
—
|
NE NERFINISHED |
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: Prince Hisahito of Akishino | Statement: [Tatsuko Kawashima, has descendant, Prince Hisahito of Akishino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has descendant Context triple: [Tatsuko Kawashima, has descendant, Prince Hisahito of Akishino]
-
A.
hasDescentTo
Indicates that one entity is a descendant of another, connected through a line of ancestry or lineage.
-
B.
hasDescent
chosen
Indicates that one entity is a descendant of another, typically through a lineage or ancestry relationship.
-
C.
possibleDescendant
Indicates that one entity may be a descendant of another, without asserting that the descendant relationship is certain.
-
D.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
E.
isGrandchildOf
Indicates that one person is the grandchild (child of a child) of another person.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6e0338c8190ace22e7a6239f68d |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:59 p.m.