Triple

T29390204
Position Surface form Disambiguated ID Type / Status
Subject SDXC E745351 entity
Predicate backwardCompatibilityNote P11993 FINISHED
Object not readable in many SDHC-only or SD-only devices 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: not readable in many SDHC-only or SD-only devices | Statement: [SDXC, backwardCompatibilityNote, not readable in many SDHC-only or SD-only devices]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: backwardCompatibilityNote
Context triple: [SDXC, backwardCompatibilityNote, not readable in many SDHC-only or SD-only devices]
  • A. backwardCompatibility
    Indicates that one entity remains functional or compatible when used with an earlier version or older form of another entity.
  • B. backwardCompatibleWith
    Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
  • C. backwardCompatibilityMethod
    Indicates that a method preserves or supports behavior from an earlier version so that older code continues to function without modification.
  • D. compatibilityNote chosen
    Indicates that there is an explanatory note or comment about how well two entities are compatible or work together.
  • E. boostCompatibility
    Indicates that one entity enhances or improves how well another entity works, interacts, or fits together with a given system, standard, or counterpart.
  • 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_69f0a79dfabc81908755382ee47791e2 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f669d648488190b7d3060432eb0eeb completed May 2, 2026, 9:17 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
Created at: April 28, 2026, 2:41 p.m.