Triple
T7377620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyotomi Tsurumatsu |
E170166
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Toyotomi |
E658250
|
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: Toyotomi | Statement: [Toyotomi Tsurumatsu, familyName, Toyotomi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Toyotomi Context triple: [Toyotomi Tsurumatsu, familyName, Toyotomi]
-
A.
Toyotomi
chosen
Toyotomi was the powerful Japanese samurai clan founded by Toyotomi Hideyoshi that briefly unified Japan in the late 16th century before being overthrown by the Tokugawa shogunate.
-
B.
Toyotomi Tsurumatsu
Toyotomi Tsurumatsu was the short-lived son and heir of Japanese warlord Toyotomi Hideyoshi during the late Sengoku period.
-
C.
Furutaka
Furutaka was a Japanese heavy cruiser of the Imperial Japanese Navy that served during the interwar period and World War II.
-
D.
Toshimichi
Toshimichi is a Japanese given name most famously borne by Ōkubo Toshimichi, a key statesman and leader of the Meiji Restoration.
-
E.
Yamamoto
Yamamoto is a Japanese surname most famously associated with Admiral Isoroku Yamamoto, the commander-in-chief of the Imperial Japanese Navy 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_69c68a5bfaac81909ce7f001dfb70c76 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1aa12888190b81e37b9fcd2adc0 |
completed | March 27, 2026, 9:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c802d57ae88190840442621d8bef35 |
completed | March 28, 2026, 4:33 p.m. |
Created at: March 27, 2026, 3:07 p.m.