Triple
T30616311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human Torch |
E779324
|
entity |
| Predicate | canCreateNovaFlame |
P112379
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Human Torch, canCreateNovaFlame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCreateNovaFlame Context triple: [Human Torch, canCreateNovaFlame, true]
-
A.
canControlFlames
chosen
Indicates the ability of one entity to generate, manipulate, or otherwise exert control over fire or flames.
-
B.
canFlyViaFlame
Indicates that an entity is capable of flying by using or generating flame as the means of propulsion or lift.
-
C.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
-
D.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
-
E.
flameHeight
Indicates the vertical extent or height reached by a flame during burning.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689ebcd0c819087ac06e22bd2e51a |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.