Triple
T7062286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takamado |
E164246
|
entity |
| Predicate | hasSurnameForm |
P18
|
FINISHED |
| Object | Takamado-no-miya |
E638959
|
NE 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: Takamado-no-miya | Statement: [Takamado, hasSurnameForm, Takamado-no-miya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Takamado-no-miya Context triple: [Takamado, hasSurnameForm, Takamado-no-miya]
-
A.
Takamado-no-miya
chosen
Takamado-no-miya is a branch of the Japanese Imperial Family traditionally associated with the title and household of Prince Takamado.
-
B.
Kizoku-in
Kizoku-in was the upper house of Japan’s prewar Imperial Diet, composed mainly of nobility and imperial appointees.
-
C.
Kasuga
Kasuga is a suburban city in Japan known for its residential communities and proximity to Fukuoka City on Kyushu Island.
-
D.
Kasuga
Kasuga was a Japanese warship active in the late 19th century, notably serving in the Boshin War as part of the modern Imperial forces.
-
E.
Fushimi-no-miya
Fushimi-no-miya is one of the oldest and most prominent shinnōke branches of the Japanese Imperial Family, historically providing potential heirs to the Chrysanthemum Throne.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e45b7488819094d2dd337731dab9 |
completed | March 27, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7944b4a60819089e565cb895c432f |
completed | March 28, 2026, 8:41 a.m. |
Created at: March 27, 2026, 2:38 p.m.