Triple

T23366276
Position Surface form Disambiguated ID Type / Status
Subject TS 42-series E593331 entity
Predicate relatedTo P37 FINISHED
Object TS 41-series — 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: TS 41-series | Statement: [TS 42-series, relatedTo, TS 41-series]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: TS 41-series
Context triple: [TS 42-series, relatedTo, TS 41-series]
  • A. TS 41-series chosen
    TS 41-series is a set of 3GPP technical specifications that define aspects of GSM/EDGE radio access and related network features within the 2G/2.5G mobile communication standards.
  • B. TS 43-series
    TS 43-series is a set of 3GPP technical specifications that define the radio access network and related aspects of GSM/EDGE and early mobile communication systems.
  • C. TS 46-series
    TS 46-series is a set of 3GPP technical specifications that define speech and audio codec standards for mobile communication systems.
  • D. TS 47-series
    TS 47-series is a set of 3GPP technical specifications that define aspects of mobile telecommunications systems, particularly in the GSM and related network domains.
  • E. TS 48-series
    The TS 48-series is a set of 3GPP technical specifications that define the interfaces and protocols for communication between core network and radio access network elements in mobile telecommunications 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_69e25d2593c88190bcdf4a716a94ccb2 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a0ac7494819082e98ac5632eba28 completed April 29, 2026, 6:09 a.m.
Created at: April 17, 2026, 5:31 p.m.