Triple

T27731440
Position Surface form Disambiguated ID Type / Status
Subject System.CLSCompliantAttribute E697438 entity
Predicate isMetadataAttribute P163121 FINISHED
Object true 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: true | Statement: [System.CLSCompliantAttribute, isMetadataAttribute, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMetadataAttribute
Context triple: [System.CLSCompliantAttribute, isMetadataAttribute, true]
  • A. isMetadataOnly
    Indicates that the referenced item exists solely as descriptive or structural metadata and does not include the actual underlying content or data.
  • B. hasMetadata
    Indicates that one entity is associated with descriptive or informational data about another entity.
  • C. isAttributeClass chosen
    Indicates that one entity functions as a defining attribute or characteristic class for another entity.
  • D. isAttributeUsageInherited
    Indicates that the use of a particular attribute by an entity is derived or carried over from its parent or ancestor rather than being defined directly on that entity.
  • E. dynamicMetadataSupport
    Indicates that the subject system or component is capable of handling metadata that can change or be updated at runtime rather than being fixed or static.
  • 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_69f63fd6c68481908c542aa03e297b9c completed May 2, 2026, 6:17 p.m.
PD Predicate disambiguation batch_69f63c6895f0819088655277e45859a8 completed May 2, 2026, 6:03 p.m.
Created at: April 27, 2026, 3:11 p.m.