Triple

T21191571
Position Surface form Disambiguated ID Type / Status
Subject ANSI X9.52 E522222 entity
Predicate definesKeyingOption P64003 FINISHED
Object two-key 3DES 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: two-key 3DES | Statement: [ANSI X9.52, definesKeyingOption, two-key 3DES]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesKeyingOption
Context triple: [ANSI X9.52, definesKeyingOption, two-key 3DES]
  • A. usesKeyingOption chosen
    Indicates that one entity employs a specific keying option or method as part of its operation or configuration.
  • B. keyType
    Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
  • C. constraintOption
    Indicates that one entity represents a specific selectable option or value that can be chosen to satisfy or configure a constraint imposed by another entity.
  • D. dominantKey
    Indicates that one musical key functions as the dominant (built on the fifth scale degree) in relation to another key.
  • E. mechanicalKeying
    Indicates that one entity physically engages or interlocks with another through a shaped mechanical interface (such as keys, slots, or profiles) to ensure correct positioning, alignment, or coupling.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e733381f288190b3da795f62a39568 completed April 21, 2026, 8:20 a.m.
PD Predicate disambiguation batch_69e5f6027c248190a170a36612bd337e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:07 p.m.