Triple
T19417180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuni no miya Kunihito |
E485751
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Kunihito |
—
|
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: Kunihito | Statement: [Kuni no miya Kunihito, givenName, Kunihito]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kunihito Context triple: [Kuni no miya Kunihito, givenName, Kunihito]
-
A.
Kuni no miya Kunihito
chosen
Kuni no miya Kunihito was a Japanese imperial prince of the collateral Kuni-no-miya branch of the Imperial Family.
-
B.
Nobuhito
Nobuhito, better known as Prince Takamatsu, was a Japanese imperial prince and the third son of Emperor Taishō, noted for his military career and postwar advocacy for peace.
-
C.
Hiyoshimaru
Hiyoshimaru was the childhood name of Kinoshita Tōkichirō, who later became the famed Japanese warlord Toyotomi Hideyoshi.
-
D.
Yoshitsugu
Yoshitsugu is a Japanese given name commonly used for males.
-
E.
Yorihito
Yorihito was a Japanese imperial prince of the Higashifushimi-no-miya house who served as a high-ranking naval officer during 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62afad8d881908f1de6324e55d2f6 |
completed | April 20, 2026, 1:32 p.m. |
Created at: April 10, 2026, 1:37 p.m.