Triple

T23363014
Position Surface form Disambiguated ID Type / Status
Subject Rel-12 E593235 entity
Predicate containsSpecification P5374 FINISHED
Object 3GPP TS 36.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 36.300 | Statement: [Rel-12, containsSpecification, 3GPP TS 36.300]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 36.300
Context triple: [Rel-12, containsSpecification, 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.101
    3GPP TS 36.101 is a technical specification that defines the user equipment (UE) radio transmission and reception requirements for LTE (E-UTRA) in the 3GPP standards.
  • C. 3GPP TS 36-series
    The 3GPP TS 36-series is a collection of technical specifications that define the LTE (4G) radio access network, including its physical layer, protocols, and procedures.
  • D. 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.
  • E. 3GPP TS 36.410
    3GPP TS 36.410 is a technical specification that defines the architecture, functions, and interfaces of the Home eNodeB Gateway within LTE mobile 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0aa0ed88190b0198cbfd1bcc59b completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:30 p.m.