Triple
T32526227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superflu |
E831321
|
entity |
| Predicate | settingImpact |
P103390
|
FINISHED |
| Object | creates post-apocalyptic world |
—
|
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: creates post-apocalyptic world | Statement: [Superflu, settingImpact, creates post-apocalyptic world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingImpact Context triple: [Superflu, settingImpact, creates post-apocalyptic world]
-
A.
exportImpact
Indicates the effect or consequences that an entity’s exports have on another entity, system, or context.
-
B.
socialImpact
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
C.
impactDescription
chosen
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
D.
encodingImpact
Indicates how one encoding or encoding choice affects, modifies, or constrains another process, representation, or outcome.
-
E.
recognizesImpactOn
Indicates that one entity acknowledges or understands the effect or consequences it has on another entity or situation.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:01 a.m.