Triple
T26147408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor Amadeus, Prince of Piedmont |
E659712
|
entity |
| Predicate | didNotSucceedBecause |
P77548
|
FINISHED |
| Object | early death |
—
|
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: early death | Statement: [Victor Amadeus, Prince of Piedmont, didNotSucceedBecause, early death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotSucceedBecause Context triple: [Victor Amadeus, Prince of Piedmont, didNotSucceedBecause, early death]
-
A.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
B.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
C.
failsTo
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
D.
didNotBecome
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
E.
failed
Indicates that an attempted action or process did not succeed in achieving its intended outcome.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be993dc819083bd352e2b444611 |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:23 p.m.