Triple
T15676266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fieschi conspiracy of 1547 |
E377451
|
entity |
| Predicate | hasCauseOfFailure |
P77548
|
FINISHED |
| Object | death of Gian Luigi Fieschi |
—
|
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: death of Gian Luigi Fieschi | Statement: [Fieschi conspiracy of 1547, hasCauseOfFailure, death of Gian Luigi Fieschi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseOfFailure Context triple: [Fieschi conspiracy of 1547, hasCauseOfFailure, death of Gian Luigi Fieschi]
-
A.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
B.
failureCause
chosen
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
C.
hasFailureProbability
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
D.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
E.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f2e10a4819097eba1ea31e36ac2 |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.