Triple
T24288068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsudaira Motoyasu |
E605729
|
entity |
| Predicate | successorNameForm |
P155706
|
FINISHED |
| Object | Tokugawa Ieyasu |
—
|
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 Ieyasu | Statement: [Matsudaira Motoyasu, successorNameForm, Tokugawa Ieyasu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorNameForm Context triple: [Matsudaira Motoyasu, successorNameForm, Tokugawa Ieyasu]
-
A.
successorFullName
Indicates that one entity is the full name of the successor of another entity (e.g., the person or role that follows it).
-
B.
successorNameChange
Indicates that an entity’s name has been changed to a new name that succeeds or replaces its previous name.
-
C.
successorNameInService
Indicates that one entity is the name of the successor that takes over a role, position, or function within a particular service or service context.
-
D.
nicknameOfSuccessor
Indicates that one entity is a nickname or informal name used to refer to another entity that is its successor.
-
E.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f57a9a08190b183879ff76071d0 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:08 a.m.