Triple

T21193262
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 36.211 E522260 entity
Predicate relatedTo P37 FINISHED
Object 3GPP TS 36.201 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 36.201 | Statement: [3GPP TS 36.211, relatedTo, 3GPP TS 36.201]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 36.201
Context triple: [3GPP TS 36.211, relatedTo, 3GPP TS 36.201]
  • A. 3GPP TS 36.201 chosen
    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.
  • B. 3GPP TS 36.321
    3GPP TS 36.321 is a technical specification that defines the Medium Access Control (MAC) protocol for the LTE (E-UTRA) radio interface in 3GPP mobile networks.
  • C. 3GPP TS 36.211
    3GPP TS 36.211 is a technical specification that defines the physical layer procedures and signal structures for LTE (E-UTRA) radio access in mobile communication systems.
  • D. 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.
  • E. 3GPP TS 36.212
    3GPP TS 36.212 is a technical specification that defines the physical layer channel coding and multiplexing procedures for the LTE (E-UTRA) radio interface.
  • 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_69e0b51061388190aa03f19700d3ef04 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e73338dbe881908360dedad65c964b completed April 21, 2026, 8:20 a.m.
Created at: April 16, 2026, 3:07 p.m.