Triple
T28665794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeitgeist (Deadpool 2) |
E725582
|
entity |
| Predicate | hasAbilityEffect |
P165537
|
FINISHED |
| Object | dissolves organic matter |
—
|
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: dissolves organic matter | Statement: [Zeitgeist (Deadpool 2), hasAbilityEffect, dissolves organic matter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbilityEffect Context triple: [Zeitgeist (Deadpool 2), hasAbilityEffect, dissolves organic matter]
-
A.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
B.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
C.
hasCharacterAbilityType
Indicates that an entity possesses a specific type or category of character ability.
-
D.
isSelectiveByAbility
Indicates that something is chosen, filtered, or differentiated based on the abilities or capabilities involved.
-
E.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 5:01 a.m.