Triple
T18971652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 秩父宮雍仁親王 |
E464183
|
entity |
| Predicate | nobleTitle |
P914
|
FINISHED |
| Object | 秩父宮 |
—
|
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: 秩父宮 | Statement: [秩父宮雍仁親王, nobleTitle, 秩父宮]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 秩父宮 Context triple: [秩父宮雍仁親王, nobleTitle, 秩父宮]
-
A.
秩父宮勢津子
秩父宮勢津子 was a Japanese princess and member of the Imperial Family, known as Princess Chichibu, who was active in cultural and charitable activities in the 20th century.
-
B.
秩父宮 雍仁親王
chosen
秩父宮 雍仁親王 was a Japanese imperial prince, younger brother of Emperor Shōwa (Hirohito), known for his military career and role in early Shōwa-era politics.
-
C.
常陸宮正仁親王
常陸宮正仁親王 is a member of the Japanese imperial family, the younger brother of Emperor Emeritus Akihito and the head of the Hitachi-no-miya household.
-
D.
秋篠宮
秋篠宮は、日本の皇室に属する皇嗣であり、天皇徳仁の弟にあたる皇族男性である。
-
E.
久邇宮邦彦王
久邇宮邦彦王 was a Japanese imperial prince of the Kuni-no-miya house who served as a senior military officer and played a prominent role in the politics and aristocracy of the late Meiji and Taishō periods.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d61a8bbc8190881908a71e0f2a53 |
completed | April 20, 2026, 7:30 a.m. |
Created at: April 10, 2026, noon