Triple
T22440280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 眞子内親王 |
E554735
|
entity |
| Predicate | 所属王朝 |
P52346
|
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.
dynastyServed
chosen
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
B.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
C.
governingDynastyAtConstruction
Indicates the ruling dynasty that held power at the time a structure or monument was constructed.
-
D.
governedPolityThroughDynasty
Indicates that a person or group exercised governing authority over a polity specifically by means of holding power within a particular dynasty.
-
E.
lastReigningDynastyOf
Indicates that one dynasty is the final ruling dynasty to have governed a particular political entity or territory.
- 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.