Triple

T1077643
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TSG SA E23873 entity
Predicate hasWorkingGroup P1382 FINISHED
Object SA4
SA4 is a 3GPP working group responsible for the standardization of multimedia codecs, systems, and services in mobile communications.
 E129976 NE FINISHED

How this triple was built (4 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: SA4 | Statement: [3GPP TSG SA, hasWorkingGroup, SA4]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SA4
Context triple: [3GPP TSG SA, hasWorkingGroup, SA4]
  • A. SA3
    SA3 is the 3GPP security working group responsible for specifying and evolving security architecture and mechanisms across mobile communication standards.
  • B. SA2
    SA2 is a 3GPP working group responsible for defining the overall system architecture and functional specifications of mobile communication networks.
  • C. SA1
    SA1 is a 3GPP working group responsible for defining overall service requirements and use cases for mobile telecommunications systems.
  • D. SAU
    SAU is the three-letter ISO 3166-1 alpha-3 country code assigned to Saudi Arabia.
  • E. SAS-4
    SAS-4 is the fourth-generation Serial Attached SCSI (SAS) interface standard that significantly increases data transfer speeds and bandwidth for enterprise storage systems.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SA4
Triple: [3GPP TSG SA, hasWorkingGroup, SA4]
Generated description
SA4 is a 3GPP working group responsible for the standardization of multimedia codecs, systems, and services in mobile communications.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: SA4
Target entity description: SA4 is a 3GPP working group responsible for the standardization of multimedia codecs, systems, and services in mobile communications.
  • A. SA3
    SA3 is the 3GPP security working group responsible for specifying and evolving security architecture and mechanisms across mobile communication standards.
  • B. SA2
    SA2 is a 3GPP working group responsible for defining the overall system architecture and functional specifications of mobile communication networks.
  • C. SA1
    SA1 is a 3GPP working group responsible for defining overall service requirements and use cases for mobile telecommunications systems.
  • D. SAU
    SAU is the three-letter ISO 3166-1 alpha-3 country code assigned to Saudi Arabia.
  • E. SAS-4
    SAS-4 is the fourth-generation Serial Attached SCSI (SAS) interface standard that significantly increases data transfer speeds and bandwidth for enterprise storage systems.
  • F. None of above. chosen

Provenance (5 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_69a493f1ddf48190a99d54b00e99f8ce completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b94288d88190aae4fb86236c0702 completed March 1, 2026, 10:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac599e543c8190bbb0558379d8d9d5 completed March 7, 2026, 5 p.m.
NEDg Description generation batch_69ac5a1fd5448190a72354c1017dfcf4 completed March 7, 2026, 5:02 p.m.
NED2 Entity disambiguation (via description) batch_69ac5a76e99c8190be49b80e31088693 completed March 7, 2026, 5:03 p.m.
Created at: March 1, 2026, 7:42 p.m.