Triple
T27811385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegiant General Pryde |
E702526
|
entity |
| Predicate | methodOfKillingHux |
P11798
|
FINISHED |
| Object | blaster shot |
—
|
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: blaster shot | Statement: [Allegiant General Pryde, methodOfKillingHux, blaster shot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfKillingHux Context triple: [Allegiant General Pryde, methodOfKillingHux, blaster shot]
-
A.
usedMethodOfKilling
Indicates that one entity employed a particular method or means to carry out a killing of another entity.
-
B.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
C.
deathMethod
chosen
Indicates the specific way or means by which a death occurred.
-
D.
finalSinkingMethod
Indicates the method or process ultimately used to sink or deliberately submerge an object, typically a vessel or structure.
-
E.
hasMannerOfDeathOfVictim
Indicates the specific way or circumstances in which the victim died in relation to the event or action being described.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 5:42 p.m.