Triple
T32526360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States military (fictional) |
E831324
|
entity |
| Predicate | hasBioweapon |
P179964
|
FINISHED |
| Object | Captain Trips |
—
|
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: Captain Trips | Statement: [United States military (fictional), hasBioweapon, Captain Trips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBioweapon Context triple: [United States military (fictional), hasBioweapon, Captain Trips]
-
A.
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.
-
B.
laterWeaponizedBy
Indicates that something was subsequently developed, adapted, or used as a weapon by a specified agent or group.
-
C.
isCarrierOf
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
-
D.
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.
-
E.
hasNuclearWeapons
Indicates that the subject possesses or controls nuclear weapons.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: May 1, 2026, 1:01 a.m.