Triple
T10119056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canningite ministry |
E223236
|
entity |
| Predicate | reasonForShortDuration |
P61770
|
FINISHED |
| Object | death of George Canning |
—
|
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 George Canning | Statement: [Canningite ministry, reasonForShortDuration, death of George Canning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForShortDuration Context triple: [Canningite ministry, reasonForShortDuration, death of George Canning]
-
A.
reasonForShortening
Indicates the explanation or cause behind why something has been shortened or reduced in length or duration.
-
B.
reasonForShortLifespan
chosen
Indicates the cause or explanation for why an entity has a relatively short lifespan.
-
C.
reasonForTime
Indicates that one entity provides the explanation or cause for a particular point or duration of time associated with another entity.
-
D.
wasShortened
Indicates that something has been made shorter in length, duration, or extent compared to its original form.
-
E.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd26460a4819093a3b239d97c3e3d |
completed | April 2, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.