Triple

T22780812
Position Surface form Disambiguated ID Type / Status
Subject TS 38-series E563829 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 38.300 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 38.300 | Statement: [TS 38-series, includes, 3GPP TS 38.300]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 38.300
Context triple: [TS 38-series, includes, 3GPP TS 38.300]
  • A. 3GPP TS 36.300
    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 28.300
    3GPP TS 28.300 is a technical specification that defines the architecture and principles for telecommunications management within 3GPP mobile networks.
  • C. 3GPP TS 38-series chosen
    The 3GPP TS 38-series is the family of 3GPP technical specifications that define the 5G New Radio (NR) air interface and related radio access network technologies.
  • D. 3GPP TS 36.304
    3GPP TS 36.304 is an LTE technical specification that defines the user equipment (UE) procedures for cell selection and reselection in E-UTRAN.
  • E. 3GPP TS 28.500
    3GPP TS 28.500 is a technical specification defining management and orchestration aspects of 5G networks within the 3GPP 28-series standards.
  • 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_69e2455500788190b4b33030461f3bbd completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17c2cab0881908df1d0629b43d350 completed April 29, 2026, 3:34 a.m.
Created at: April 17, 2026, 3:28 p.m.