Triple

T23218026
Position Surface form Disambiguated ID Type / Status
Subject TS 31-series E580803 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 31.115 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 31.115 | Statement: [TS 31-series, includes, 3GPP TS 31.115]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 31.115
Context triple: [TS 31-series, includes, 3GPP TS 31.115]
  • A. 3GPP TS 31.115 chosen
    3GPP TS 31.115 is a technical specification within the 3GPP 31-series that defines aspects of the interface and behavior related to UICC/SIM applications in mobile communication systems.
  • B. 3GPP TS 31.111
    3GPP TS 31.111 is a technical specification that defines the interface and procedures for the SIM Application Toolkit (SAT) in mobile communication systems.
  • C. 3GPP TS 32.111
    3GPP TS 32.111 is a technical specification within the 3GPP 32-series that defines aspects of telecommunications network management, particularly related to alarm and fault management.
  • D. 3GPP TS 26.515
    3GPP TS 26.515 is a technical specification within the 3GPP 26-series that defines aspects of multimedia codecs and related media handling for mobile communication systems.
  • E. 3GPP TS 31.131
    3GPP TS 31.131 is a technical specification that defines the characteristics and testing requirements for UICC-based applications and interfaces in mobile communication systems.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1916653f08190a7dcbc659c6b6a25 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.