Triple

T22847707
Position Surface form Disambiguated ID Type / Status
Subject TS 23-series E566266 entity
Predicate relatedTo P37 FINISHED
Object TS 29-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 29-series | Statement: [TS 23-series, relatedTo, TS 29-series]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: TS 29-series
Context triple: [TS 23-series, relatedTo, TS 29-series]
  • A. TS 29-series chosen
    The TS 29-series is a collection of 3GPP technical specifications that define core network interfaces, protocols, and procedures for mobile telecommunications systems.
  • B. TS 26-series
    TS 26-series is a collection of 3GPP technical specifications that define audio, video, and multimedia codecs and related media handling for mobile communication systems.
  • C. TS 23-series
    TS 23-series is a set of 3GPP system architecture and service-level technical specifications that define how mobile networks and their services are structured and interoperate.
  • D. TS 24-series
    The TS 24-series is a collection of 3GPP technical specifications that define core signaling, call control, and session management protocols for mobile and IP-based telecommunications networks.
  • E. TS 22-series
    TS 22-series is a set of 3GPP technical specifications that define service requirements and features for 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e89ab348190a31260221195ae67 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.