Triple
T29599209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darth Malak |
E754392
|
entity |
| Predicate | usedSuperweapon |
P706
|
FINISHED |
| Object | Star Forge |
—
|
NE NERFINISHED |
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: Star Forge | Statement: [Darth Malak, usedSuperweapon, Star Forge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSuperweapon Context triple: [Darth Malak, usedSuperweapon, Star Forge]
-
A.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
B.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
C.
usedAsWarheadFor
Indicates that something functions as the explosive or destructive payload component for a specified weapon or delivery system.
-
D.
weaponizedAs
Indicates that something has been adapted, modified, or used for the purpose of causing harm, damage, or coercion, effectively turning it into a weapon.
-
E.
usedWeapon
chosen
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66dba1e208190bc145461b8334701 |
completed | May 2, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:20 p.m.