Triple

T5480958
Position Surface form Disambiguated ID Type / Status
Subject Network Slice Selection Function E123464 entity
Predicate definedIn P775 FINISHED
Object 3GPP TS 29.531 E127338 NE FINISHED

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 29.531 | Statement: [Network Slice Selection Function, definedIn, 3GPP TS 29.531]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.531
Context triple: [Network Slice Selection Function, definedIn, 3GPP TS 29.531]
  • A. 3GPP TS 36.331
    3GPP TS 36.331 is a 3GPP technical specification that defines the Radio Resource Control (RRC) protocol for LTE (E-UTRA) networks.
  • B. 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.
  • C. 3GPP TS 23.401
    3GPP TS 23.401 is a core 3GPP technical specification that defines the system architecture and procedures for packet-switched services in LTE/Evolved Packet Core networks.
  • D. 3GPP TS 29-series chosen
    The 3GPP TS 29-series is a collection of technical specifications that define core network interfaces and protocols within 3GPP mobile communication systems.
  • E. 3GPP TS 23.203
    3GPP TS 23.203 is a 3GPP technical specification that defines the policy and charging control architecture and mechanisms for QoS management in mobile networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd924a2eb08190b759b23a6eab5e0a completed March 20, 2026, 6:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf70d919e08190a4fae4359cf8c951 completed March 22, 2026, 4:32 a.m.
Created at: March 20, 2026, 2:09 p.m.