Triple

T25131028
Position Surface form Disambiguated ID Type / Status
Subject Josephson voltage standard E629521 entity
Predicate programmableTypeUses P157954 FINISHED
Object pulse-driven Josephson junction arrays 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: pulse-driven Josephson junction arrays | Statement: [Josephson voltage standard, programmableTypeUses, pulse-driven Josephson junction arrays]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: programmableTypeUses
Context triple: [Josephson voltage standard, programmableTypeUses, pulse-driven Josephson junction arrays]
  • A. containsProgramType
    Indicates that one entity includes or encompasses a specific type or category of program.
  • B. usedByProgram
    Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
  • C. usedAsProgramFor
    Indicates that one entity functions as the software or application used to operate, control, or provide services for another entity.
  • D. usedInType
    Indicates that something serves as a component, element, or example within a particular type or category.
  • E. hasProgramTypeRestriction
    Indicates that there is a constraint limiting which types of programs are allowed or applicable in a given context.
  • F. None of above. chosen

Provenance (4 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_69e2ff338250819096ff6c8892804389 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f465f9abe48190863be7824dcbd48c completed May 1, 2026, 8:36 a.m.
PD Predicate disambiguation batch_69f44d8043b081908bbffd7f044b4f26 completed May 1, 2026, 6:51 a.m.
PDg Predicate description generation batch_69f45300bd488190bb1d4160f5534ef6 completed May 1, 2026, 7:15 a.m.
Created at: April 18, 2026, 6:28 a.m.