Triple
T27087552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Asaka Yuriko |
E686075
|
entity |
| Predicate | monarchicBranch |
P13166
|
FINISHED |
| Object | Asaka branch |
—
|
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: Asaka branch | Statement: [Princess Asaka Yuriko, monarchicBranch, Asaka branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchicBranch Context triple: [Princess Asaka Yuriko, monarchicBranch, Asaka branch]
-
A.
monarchicalHouse
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical house or dynasty.
-
B.
dynasticBranch
chosen
Indicates a genealogical relationship where one lineage or house originates from, or is a subordinate offshoot of, a larger parent dynasty.
-
C.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
D.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
E.
hereditaryMonarch
Indicates that a person holds a monarchical position that is passed down through a family line according to hereditary succession rules.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 8:38 a.m.