Triple
T27319913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokugawa Tadanaga |
E689460
|
entity |
| Predicate | successorInDomain |
P185935
|
FINISHED |
| Object | Tokugawa Iemitsu |
—
|
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: Tokugawa Iemitsu | Statement: [Tokugawa Tadanaga, successorInDomain, Tokugawa Iemitsu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInDomain Context triple: [Tokugawa Tadanaga, successorInDomain, Tokugawa Iemitsu]
-
A.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
B.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
C.
successorInRegion
Indicates that one entity directly follows or replaces another within a specified region or jurisdiction.
-
D.
successorFunctionally
Indicates that one entity functionally replaces or follows another in performing the same role, task, or purpose.
-
E.
successorFoundedBy
Indicates that an entity was founded by the successor of another specified entity.
- F. None of above. chosen
Provenance (4 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: April 27, 2026, 11:32 a.m.