Triple

T18553220
Position Surface form Disambiguated ID Type / Status
Subject SAE E453434 entity
Predicate roleInWPA3 P132134 FINISHED
Object primary authentication and key establishment method for WPA3-Personal 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: primary authentication and key establishment method for WPA3-Personal | Statement: [SAE, roleInWPA3, primary authentication and key establishment method for WPA3-Personal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInWPA3
Context triple: [SAE, roleInWPA3, primary authentication and key establishment method for WPA3-Personal]
  • A. roleIn3GPP
    Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
  • B. roleInGateway
    Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
  • C. protectionRole
    Indicates that one entity serves a protective function or responsibility toward another entity or resource.
  • D. airGroupRole
    Indicates the specific function or duty an air group performs within a larger operation or organizational context.
  • E. ClientRole
    Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
  • 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e538027b94819082a4c4af66e170d7 completed April 19, 2026, 8:16 p.m.
PD Predicate disambiguation batch_69e469e274a48190a570b25cfef4d890 completed April 19, 2026, 5:36 a.m.
PDg Predicate description generation batch_69e46d2b93bc8190a6070018d7046547 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 11:38 a.m.