Triple

T5480108
Position Surface form Disambiguated ID Type / Status
Subject QCI (QoS Class Identifier) E123447 entity
Predicate specifiedIn P775 FINISHED
Object 3GPP TS 36.300 E522259 NE 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: 3GPP TS 36.300 | Statement: [QCI (QoS Class Identifier), specifiedIn, 3GPP TS 36.300]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 36.300
Context triple: [QCI (QoS Class Identifier), specifiedIn, 3GPP TS 36.300]
  • A. 3GPP TS 36.300 chosen
    3GPP TS 36.300 is a technical specification that defines the overall architecture and functions of the LTE (E-UTRAN) radio access network within the 3GPP standards.
  • B. 3GPP TS 36.201
    3GPP TS 36.201 is a technical specification that defines the physical layer aspects of the LTE (E-UTRA) radio interface in 3GPP mobile communication systems.
  • C. 3GPP TS 36.331
    3GPP TS 36.331 is a 3GPP technical specification that defines the Radio Resource Control (RRC) protocol for LTE (E-UTRA) networks.
  • D. 3GPP TS 23.401
    3GPP TS 23.401 is a core 3GPP technical specification that defines the system architecture and procedures for packet-switched services in LTE/Evolved Packet Core networks.
  • E. 3GPP TS 31-series
    The 3GPP TS 31-series is a set of technical specifications that define the interface, protocols, and application toolkit behavior for UICC/SIM/USIM cards in mobile communication systems.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd9248ca348190aa116cace0f9b07a completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf77b59ef881909c5968194336b101 completed March 22, 2026, 5:01 a.m.
Created at: March 20, 2026, 2:09 p.m.