Triple

T27736759
Position Surface form Disambiguated ID Type / Status
Subject System.Reflection.AssemblyConfigurationAttribute E697546 entity
Predicate affectsRuntimeBehavior P169948 FINISHED
Object false 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: false | Statement: [System.Reflection.AssemblyConfigurationAttribute, affectsRuntimeBehavior, false]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: affectsRuntimeBehavior
Context triple: [System.Reflection.AssemblyConfigurationAttribute, affectsRuntimeBehavior, false]
  • A. affectsBehaviorOf
    Indicates that one entity produces a change or influence on the behavior, actions, or conduct of another entity.
  • B. affectsProgram
    Indicates that one entity produces an influence or change on a program, altering its behavior, state, or outcome.
  • C. affectsProcess
    Indicates that one entity has an influence on, alters, or changes the course or outcome of a process.
  • D. runTimeSupport
    Indicates that one entity provides or requires support for another entity during its execution at run time.
  • E. isRuntimeEnforced
    Indicates that a rule, constraint, or condition is actively checked and enforced during program execution rather than at compile time or design time.
  • 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_69f688d015908190ad5df37030ecf332 completed May 2, 2026, 11:29 p.m.
PD Predicate disambiguation batch_69f68609c0b08190a8e1238a4d97c270 completed May 2, 2026, 11:17 p.m.
PDg Predicate description generation batch_69f688034580819086a0f9100645f8ba completed May 2, 2026, 11:25 p.m.
Created at: April 27, 2026, 3:13 p.m.