Triple
T35648028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Praetor Shinzon |
E1030060
|
entity |
| Predicate | methodOfSeizingPower |
P136123
|
FINISHED |
| Object | assassination of the Romulan Senate |
—
|
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: assassination of the Romulan Senate | Statement: [Praetor Shinzon, methodOfSeizingPower, assassination of the Romulan Senate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfSeizingPower Context triple: [Praetor Shinzon, methodOfSeizingPower, assassination of the Romulan Senate]
-
A.
seizedPowerBy
Indicates that one entity took control or authority from another, typically through force, coercion, or other non-consensual means.
-
B.
methodOfExercisingPower
Indicates the specific way or mechanism through which power or authority is exercised or applied in a given context.
-
C.
meansOfPowerAcquisition
chosen
Indicates the method or process through which an entity obtains or gains power or authority.
-
D.
assignsExecutivePowerTo
Indicates that executive authority or decision-making power is formally granted from one entity to another.
-
E.
seizedPowerAfter
Indicates that one entity took control or authority from another entity following a specified event or point in time.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.