Triple

T37458740
Position Surface form Disambiguated ID Type / Status
Subject Piloted Shredder E930863 entity
Predicate synergy P134654 FINISHED
Object Synergizes with Mechwarper 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: Synergizes with Mechwarper | Statement: [Piloted Shredder, synergy, Synergizes with Mechwarper]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: synergy
Context triple: [Piloted Shredder, synergy, Synergizes with Mechwarper]
  • A. actsSynergisticallyWith chosen
    Indicates that two entities interact in a way that enhances or amplifies each other's effects or outcomes beyond what they would achieve independently.
  • B. raceSynergy
    Indicates how the combination of different races or species enhances, modifies, or interacts to affect overall effectiveness or outcome.
  • C. statSynergy
    Indicates a relationship where the combined or interacting statistics of entities produce enhanced or altered effects compared to their individual contributions.
  • D. syn
    Indicates that two entities are synonyms, expressing the same or nearly the same meaning in a given context.
  • E. sharesTelepathicBondWith
    Indicates a mutual telepathic connection through which two entities can directly share thoughts, feelings, or information.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaebc8f2c8190b94f1b4a3ec92e8c completed May 6, 2026, 9:12 p.m.
PD Predicate disambiguation batch_69fbadf1e6008190a71bbd196ba06844 completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:17 p.m.