Triple

T21345795
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 24.503 E526332 entity
Predicate shortName P43 FINISHED
Object TS 24.503 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: TS 24.503 | Statement: [3GPP TS 24.503, shortName, TS 24.503]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TS 24.503
Context triple: [3GPP TS 24.503, shortName, TS 24.503]
  • A. 3GPP TS 24.503 chosen
    3GPP TS 24.503 is a technical specification that defines the Non-Access Stratum (NAS) signaling procedures for 5G system (5GS) mobile devices and networks.
  • B. 3GPP TS 24.502
    3GPP TS 24.502 is a technical specification defining key non-access stratum (NAS) signaling procedures and protocols for 5G system operation within the 3GPP standards framework.
  • C. 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.
  • D. 3GPP TS 29.503
    3GPP TS 29.503 is a technical specification defining core network interfaces and procedures within the 3GPP 29-series for mobile telecommunications systems.
  • E. 3GPP TS 23.502
    3GPP TS 23.502 is a 5G system architecture specification that defines procedures and interactions between core network functions for access, mobility, and session management.
  • 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_69e0b51cd5cc81909ac1187971e8a8ad completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e8a854e8ec81909efd41c1e959cc61 completed April 22, 2026, 10:52 a.m.
Created at: April 16, 2026, 4:54 p.m.