Triple
T7318022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyotomi Hideyori |
E168462
|
entity |
| Predicate | deathResultedIn |
P76271
|
FINISHED |
| Object | elimination of Toyotomi political power |
—
|
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: elimination of Toyotomi political power | Statement: [Toyotomi Hideyori, deathResultedIn, elimination of Toyotomi political power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathResultedIn Context triple: [Toyotomi Hideyori, deathResultedIn, elimination of Toyotomi political power]
-
A.
deathOutcome
Indicates that an event, condition, or action results in the death of the affected entity.
-
B.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
C.
deathCharacteristic
Indicates a characteristic, attribute, or quality specifically associated with a death event or the manner in which death occurred.
-
D.
deathContributedTo
Indicates that one entity played a causal or contributing role in bringing about the death of another entity.
-
E.
deathApprox
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef178b3081908cd0c62466069741 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:02 p.m.