Triple
T15385871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Starkiller Base |
E367913
|
entity |
| Predicate | superweaponType |
P89527
|
FINISHED |
| Object | planet-killing superlaser |
—
|
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: planet-killing superlaser | Statement: [Battle of Starkiller Base, superweaponType, planet-killing superlaser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superweaponType Context triple: [Battle of Starkiller Base, superweaponType, planet-killing superlaser]
-
A.
warheadTypes
Indicates the types or categories of warheads associated with a given weapon or delivery system.
-
B.
weaponSystemType
chosen
Indicates the specific category or kind of weapon system associated with an entity.
-
C.
isStrategicWeapon
Indicates that the weapon is designed or classified for large-scale, long-range, or high-impact strategic use rather than for tactical or localized operations.
-
D.
weaponCapability
Indicates that one entity has the ability to use, deploy, or function as a weapon against another entity or target.
-
E.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e74ff70819094c1a85f51d6e228 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.