Triple

T9029471
Position Surface form Disambiguated ID Type / Status
Subject RenVM E216131 entity
Predicate burns P85972 FINISHED
Object wrapped assets to release native assets on origin chains 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: wrapped assets to release native assets on origin chains | Statement: [RenVM, burns, wrapped assets to release native assets on origin chains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: burns
Context triple: [RenVM, burns, wrapped assets to release native assets on origin chains]
  • A. burnType
    Indicates the specific category or severity of a burn associated with an entity or event.
  • B. burned
    Indicates that one entity caused another entity to be damaged or consumed by fire or intense heat.
  • C. burnedDuring
    Indicates that one event, object, or process was actively burning or being consumed by fire during the time span of another specified event or interval.
  • D. burningSince
    Indicates that an object or substance has been continuously burning from a specified starting time up to the present or another reference time.
  • E. fires
    Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
  • 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_69ca83a5fa88819088144801b4dd7245 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6a9bcb508190b58751f1772407d4 completed April 1, 2026, 12:45 a.m.
PD Predicate disambiguation batch_69cc5ee132f08190940749c7c522e4c1 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f887108819096d45a186fc137b3 completed March 31, 2026, 11:58 p.m.
Created at: March 30, 2026, 7:08 p.m.