Triple
T12977499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinoshita Tōkichirō |
E321565
|
entity |
| Predicate | heldTitle |
P8
|
FINISHED |
| Object | Kampaku |
E408079
|
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: Kampaku | Statement: [Kinoshita Tōkichirō, heldTitle, Kampaku]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kampaku Context triple: [Kinoshita Tōkichirō, heldTitle, Kampaku]
-
A.
Kampaku
chosen
Kampaku was a powerful regent position in Japan’s imperial court, typically held by senior aristocrats who governed on behalf of an adult emperor.
-
B.
Kujō
Kujō is a Japanese surname historically associated with an aristocratic kuge family that was part of the influential Fujiwara clan.
-
C.
Narusawa
Narusawa is a village in Yamanashi Prefecture, Japan, located in the scenic Fuji Five Lakes region near Mount Fuji.
-
D.
Sadanaru
Sadanaru is a Japanese given name historically borne by members of the imperial family, including Prince Fushimi Sadanaru.
-
E.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e48c0208190bb7ec80780480b37 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8f0315c8190aae5908ba65d5867 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:38 p.m.