Triple
T28986914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Asaka Kiyoko |
E734710
|
entity |
| Predicate | branchOfImperialHouse |
P136709
|
FINISHED |
| Object | Asaka branch |
—
|
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: Asaka branch | Statement: [Princess Asaka Kiyoko, branchOfImperialHouse, Asaka branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchOfImperialHouse Context triple: [Princess Asaka Kiyoko, branchOfImperialHouse, Asaka branch]
-
A.
hasBranchOfImperialFamily
chosen
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
B.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
C.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
D.
generationWithinImperialFamily
Indicates the ordinal generation level of an individual within an imperial family lineage (e.g., first generation, second generation).
-
E.
dynasticBranch
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65f7a782081909a7915941423bdd3 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:15 a.m.