Triple
T14578925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōishi |
E342131
|
entity |
| Predicate | honorificTitle |
P2097
|
FINISHED |
| Object | Kuranosuke |
E1174846
|
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: Kuranosuke | Statement: [Ōishi, honorificTitle, Kuranosuke]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kuranosuke Context triple: [Ōishi, honorificTitle, Kuranosuke]
-
A.
Kuranosuke
chosen
Kuranosuke is the given name of Ōishi Kuranosuke, the historical leader of the Forty-seven rōnin in early 18th-century Japan.
-
B.
Kenjirō
Kenjirō is a Japanese masculine given name that can be written with various kanji combinations and is borne by multiple notable individuals in fields such as sports, arts, and entertainment.
-
C.
Kinsaku
Kinsaku is the birth name of Matsuo Bashō, the renowned 17th-century Japanese haiku poet and literary figure.
-
D.
Kinnosuke
Kinnosuke is the given name of the renowned Japanese novelist Natsume Sōseki, a central figure in modern Japanese literature.
-
E.
Harukichi
Harukichi is a Japanese given name most notably borne by Harukichi Hyakutake, an Imperial Japanese Navy admiral during World War II.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff9976bc888190a050c2502d1f8e81 |
completed | May 9, 2026, 8:30 p.m. |
Created at: April 10, 2026, 1:24 a.m.