Triple
T28545289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunpu |
E722418
|
entity |
| Predicate | roleForTokugawaIeyasu |
P146698
|
FINISHED |
| Object | retirement residence |
—
|
LITERAL 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: retirement residence | Statement: [Sunpu, roleForTokugawaIeyasu, retirement residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleForTokugawaIeyasu Context triple: [Sunpu, roleForTokugawaIeyasu, retirement residence]
-
A.
rankWithinTokugawa
Indicates the relative hierarchical position or status an entity holds within the Tokugawa-era ranking system.
-
B.
roleInEdoPeriod
chosen
Indicates that an entity held a specific role, position, or function during Japan’s Edo period.
-
C.
sideInBattleOfSekigahara
Indicates that an entity participated as a side or faction in the Battle of Sekigahara.
-
D.
opponentAtSekigahara
Indicates that two entities were opposing sides against each other in the Battle of Sekigahara.
-
E.
successorAsDaimyoOfHikone
Indicates that one entity became the next daimyō (feudal lord) of Hikone, directly succeeding another in that position.
- F. None of above.
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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6500cefa88190a7e9464fc428bc23 |
completed | May 2, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:38 a.m.