Triple

T9695600
Position Surface form Disambiguated ID Type / Status
Subject Sokovia E234640 entity
Predicate impactOnMCU P40373 FINISHED
Object catalyst for international regulation of superheroes 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: catalyst for international regulation of superheroes | Statement: [Sokovia, impactOnMCU, catalyst for international regulation of superheroes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: impactOnMCU
Context triple: [Sokovia, impactOnMCU, catalyst for international regulation of superheroes]
  • A. hasMicrocontroller
    Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
  • B. impactOnPerformance
    Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
  • C. hasMicrocontrollerCore
    Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
  • D. effectOnSystem chosen
    Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
  • E. mcuVersion
    Indicates the specific version or revision identifier of a microcontroller unit (MCU) associated with an entity.
  • 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_69ca84cb580c8190a7e5f4b3bcdaf2a4 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9d366c488190bc153c68fef197c2 completed April 1, 2026, 10:33 p.m.
PD Predicate disambiguation batch_69ccd5b9e93c8190947cce56a3925364 completed April 1, 2026, 8:22 a.m.
Created at: March 30, 2026, 8:17 p.m.