Triple
T28421065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demon core |
E719940
|
entity |
| Predicate | weaponDesignContext |
P128826
|
FINISHED |
| Object | implosion-type nuclear weapon |
—
|
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: implosion-type nuclear weapon | Statement: [Demon core, weaponDesignContext, implosion-type nuclear weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponDesignContext Context triple: [Demon core, weaponDesignContext, implosion-type nuclear weapon]
-
A.
weaponDesigner
Indicates that one entity is the creator or designer of a weapon used or associated with another entity.
-
B.
turretDesign
Indicates a relationship where one entity specifies or defines the design or configuration of a turret associated with another entity.
-
C.
tacticalDesignConcept
Indicates a conceptual plan or approach that defines how tactical actions or operations should be structured and executed.
-
D.
nuclearWeaponDesign
chosen
Indicates that an entity is involved in the creation, specification, or technical configuration of a nuclear weapon.
-
E.
bulletDesignation
Indicates that one entity is designated or labeled as a specific bullet point or bullet-style marker in relation to another entity.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:33 a.m.