Triple

T27737322
Position Surface form Disambiguated ID Type / Status
Subject System.Reflection.PropertyAttributes E697559 entity
Predicate valueOf_HasDefault P128025 FINISHED
Object 4096 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: 4096 | Statement: [System.Reflection.PropertyAttributes, valueOf_HasDefault, 4096]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: valueOf_HasDefault
Context triple: [System.Reflection.PropertyAttributes, valueOf_HasDefault, 4096]
  • A. hasZeroDefaultValue
    Indicates that the associated entity or attribute is defined to have a default value of zero when no explicit value is provided.
  • B. defaultValue chosen
    Indicates that one entity serves as the pre-assigned or fallback value automatically used for another entity when no explicit value is provided.
  • C. hasValue
    Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
  • D. isDefaultFor
    Indicates that something serves as the standard or fallback option that is automatically applied or selected for a given entity or context unless another choice is explicitly specified.
  • E. valueDefinedBy
    Indicates that the value of one entity is determined, specified, or constrained by another 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_69ef590c3e288190ad54d2465af8ca4e completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69f6617ba4a88190bfc5c305acb4f93f completed May 2, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69f660f082508190a95a7888ad66cb2e completed May 2, 2026, 8:39 p.m.
Created at: April 27, 2026, 3:13 p.m.