Triple

T22062771
Position Surface form Disambiguated ID Type / Status
Subject AUSF E545192 entity
Predicate definedIn P775 FINISHED
Object 3GPP TS 33.501 NE NERFINISHED

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: 3GPP TS 33.501 | Statement: [AUSF, definedIn, 3GPP TS 33.501]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 33.501
Context triple: [AUSF, definedIn, 3GPP TS 33.501]
  • A. 3GPP TS 33.501 chosen
    3GPP TS 33.501 is a 5G security specification that defines the overall security architecture, procedures, and mechanisms for 5G System networks.
  • B. 3GPP TS 29.501
    3GPP TS 29.501 is a technical specification that defines the system architecture and core network signaling interfaces for 5G networks within the 3GPP standards framework.
  • C. 3GPP TS 33.401
    3GPP TS 33.401 is a technical specification that defines the security architecture and procedures for LTE/Evolved Packet System networks.
  • D. 3GPP TS 24.501
    3GPP TS 24.501 is a technical specification that defines the Non-Access Stratum (NAS) protocol for 5G system procedures, including registration, session management, and mobility management between user equipment and the core network.
  • E. 3GPP TS 23.501
    3GPP TS 23.501 is a core 5G system specification that defines the overall system architecture, procedures, and key network functions for 5G networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285e8c688190b701e417893cc148 completed April 28, 2026, 9:36 p.m.
Created at: April 16, 2026, 8:27 p.m.