Triple

T5307138
Position Surface form Disambiguated ID Type / Status
Subject The AllSpark E120128 entity
Predicate fragmentEffect P39638 FINISHED
Object uncontrolled or corrupted transformations 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: uncontrolled or corrupted transformations | Statement: [The AllSpark, fragmentEffect, uncontrolled or corrupted transformations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fragmentEffect
Context triple: [The AllSpark, fragmentEffect, uncontrolled or corrupted transformations]
  • A. visualEffect
    Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
  • B. specialEffectsBy
    Indicates that the special effects for something (such as a film, scene, or shot) are created or provided by a particular person or entity.
  • C. fireEffect
    Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
  • D. sideEffect chosen
    Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
  • E. eventEffect
    Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
  • 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_69bd44704be88190acdb2ac481b0ff55 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd86f20f008190be7b5848af05f2b8 completed March 20, 2026, 5:42 p.m.
PD Predicate disambiguation batch_69bd84534f9c8190bc19d4812060768d completed March 20, 2026, 5:30 p.m.
Created at: March 20, 2026, 1:53 p.m.