Triple

T27731321
Position Surface form Disambiguated ID Type / Status
Subject System.SerializableAttribute E697436 entity
Predicate hasAttributeUsage P163524 FINISHED
Object AttributeTargets.Struct NE NERFINISHED

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: AttributeTargets.Struct | Statement: [System.SerializableAttribute, hasAttributeUsage, AttributeTargets.Struct]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAttributeUsage
Context triple: [System.SerializableAttribute, hasAttributeUsage, AttributeTargets.Struct]
  • A. hasAttributeUsage chosen
    Indicates that an entity uses or applies a particular attribute in some context or manner.
  • B. 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.
  • C. usesAttribute
    Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
  • D. hasVariantUsage
    Indicates that an entity is used in an alternative or non-standard way compared to its primary or canonical usage.
  • E. hasUsageLevel
    Indicates the degree or intensity with which something is used or utilized.
  • 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.