Triple
T31068767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineers on Planet 4 |
E791754
|
entity |
| Predicate | bioweaponType |
P60876
|
FINISHED |
| Object | black goo pathogen |
—
|
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: black goo pathogen | Statement: [Engineers on Planet 4, bioweaponType, black goo pathogen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bioweaponType Context triple: [Engineers on Planet 4, bioweaponType, black goo pathogen]
-
A.
pathogenType
Indicates the specific kind or category of pathogen associated with or responsible for an entity or condition.
-
B.
destroyedChemicalAgent
Indicates that an entity has rendered a chemical agent unusable or eliminated it, typically through neutralization, dismantling, or disposal.
-
C.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
D.
isPathogenOf
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
E.
weaponizedAs
chosen
Indicates that something has been adapted, modified, or used for the purpose of causing harm, damage, or coercion, effectively turning it into a weapon.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6957d170c8190bfd0bed26b8d1d30 |
completed | May 3, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:01 p.m.