Triple

T32123079
Position Surface form Disambiguated ID Type / Status
Subject NSCoding E820430 entity
Predicate requiresConformance P5499 FINISHED
Object NSObject subclasses (typical) 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: NSObject subclasses (typical) | Statement: [NSCoding, requiresConformance, NSObject subclasses (typical)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresConformance
Context triple: [NSCoding, requiresConformance, NSObject subclasses (typical)]
  • A. definesConformanceRequirementsFor
    Indicates that one entity specifies the rules, criteria, or conditions that another entity must satisfy to be considered conformant.
  • B. hasConformanceRequirements chosen
    Indicates that an entity is subject to specific rules, standards, or criteria that it must satisfy or comply with.
  • C. usesConformanceLevels
    Indicates that one entity applies or adheres to defined conformance levels when interacting with or evaluating another entity.
  • D. conformanceType
    Indicates the specific manner or degree to which one entity adheres to, complies with, or satisfies the requirements, rules, or expectations defined by another.
  • E. requiresComplianceTestingBy
    Indicates that one entity must undergo compliance testing conducted or overseen 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_69f34902d42c819083a8e6bba9a8bb9a completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fed6da0390819096b88ef4714b144e completed May 9, 2026, 6:40 a.m.
PD Predicate disambiguation batch_69fed53517d081909966f31707625f1a completed May 9, 2026, 6:33 a.m.
Created at: May 1, 2026, 12:29 a.m.