Triple
T25949255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genii |
E653924
|
entity |
| Predicate | developsWeapon |
P35807
|
FINISHED |
| Object | fission nuclear bomb |
—
|
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: fission nuclear bomb | Statement: [Genii, developsWeapon, fission nuclear bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsWeapon Context triple: [Genii, developsWeapon, fission nuclear bomb]
-
A.
weaponDesigner
Indicates that one entity is the creator or designer of a weapon used or associated with another entity.
-
B.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
C.
introducedWeaponSystem
chosen
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
-
D.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
E.
featuredWeapon
Indicates that a particular weapon is highlighted or prominently showcased in relation to an entity, such as a character, event, or context.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 22, 2026, 8:43 a.m.