Triple

T27737398
Position Surface form Disambiguated ID Type / Status
Subject System.Reflection.PortableExecutableKinds E697561 entity
Predicate NotAPortableExecutableImage_value P163172 FINISHED
Object 0 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: 0 | Statement: [System.Reflection.PortableExecutableKinds, NotAPortableExecutableImage_value, 0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: NotAPortableExecutableImage_value
Context triple: [System.Reflection.PortableExecutableKinds, NotAPortableExecutableImage_value, 0]
  • A. isPortable
    Indicates that an object can be easily moved or carried from one place to another without significant effort or setup.
  • B. isLessPortableThan
    Indicates that one entity is more difficult to move, carry, or transport than another entity.
  • C. isPortableComparedTo
    Indicates that one entity can be moved, carried, or transported more easily than another entity.
  • D. notNativeTo
    Indicates that an entity does not originate from, or is not naturally occurring in, a specified place or environment.
  • E. supportsDiskImageFormat
    Indicates that one entity is capable of handling, using, or being compatible with a specified disk image format.
  • 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f636a161608190b0cdf03863204034 completed May 2, 2026, 5:38 p.m.
PD Predicate disambiguation batch_69f63188e7408190af8ce8b93d128c63 completed May 2, 2026, 5:16 p.m.
PDg Predicate description generation batch_69f6352df6148190bc10772cd40bd7b3 completed May 2, 2026, 5:32 p.m.
Created at: April 27, 2026, 3:13 p.m.