Triple
T23340208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amazing Colossal Man |
E591714
|
entity |
| Predicate | featuredWeapon |
P151929
|
FINISHED |
| Object | plutonium 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: plutonium bomb | Statement: [The Amazing Colossal Man, featuredWeapon, plutonium bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredWeapon Context triple: [The Amazing Colossal Man, featuredWeapon, plutonium bomb]
-
A.
formerWeapon
Indicates that an entity once functioned as a weapon but no longer serves in that role.
-
B.
swordsFeature
Indicates that something includes or prominently presents swords as a notable element or characteristic.
-
C.
specialWeapon
Indicates that an entity is a weapon with unique, enhanced, or otherwise exceptional properties compared to standard weapons.
-
D.
symbolicWeapon
Indicates a relationship where something functions as a symbolic or emblematic weapon for an entity, representing power, threat, or conflict rather than serving as a literal physical armament.
-
E.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
- F. None of above. chosen
Provenance (4 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198317f4c8190a557cacb86568d6c |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:18 p.m.