Triple

T26408566
Position Surface form Disambiguated ID Type / Status
Subject NIST E663895 entity
Predicate focusInAESSubsetContext P86548 FINISHED
Object selection and standardization of Rijndael as AES 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: selection and standardization of Rijndael as AES | Statement: [NIST, focusInAESSubsetContext, selection and standardization of Rijndael as AES]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: focusInAESSubsetContext
Context triple: [NIST, focusInAESSubsetContext, selection and standardization of Rijndael as AES]
  • A. focusOf chosen
    Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
  • B. focusesBy
    Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
  • C. focusShift
    Indicates a change in attention or emphasis from one entity or topic to another.
  • D. focusModel
    Indicates that one entity serves as the primary or central model that another entity is directed toward, based on, or concentrated on.
  • E. focusType
    Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
  • 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_69ee883931888190901be96d75ee23cc completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 26, 2026, 11:36 p.m.