Triple
T28518321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Sasha |
E721685
|
entity |
| Predicate | deathConspiracy |
P167364
|
FINISHED |
| Object | part of Flagg’s plot against the royal family |
—
|
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: part of Flagg’s plot against the royal family | Statement: [Queen Sasha, deathConspiracy, part of Flagg’s plot against the royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathConspiracy Context triple: [Queen Sasha, deathConspiracy, part of Flagg’s plot against the royal family]
-
A.
deathCoveredUpBy
Indicates that a death was intentionally concealed, misrepresented, or hidden by a particular agent or entity.
-
B.
deathPrecedes
Indicates that one entity’s death occurs earlier in time than another specified event or entity’s death.
-
C.
deathEpisode
Indicates the episode or event in which an entity’s death occurs or is depicted.
-
D.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
E.
deathOvers
Indicates the number of overs bowled in the final phase of a limited-overs cricket innings, typically focused on the closing overs where scoring and wicket-taking intensify.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 3:18 a.m.