Triple

T5771333
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TSG CT E127336 entity
Predicate hasWorkingGroup P1382 FINISHED
Object CT WG6 E132535 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: CT WG6 | Statement: [3GPP TSG CT, hasWorkingGroup, CT WG6]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: CT WG6
Context triple: [3GPP TSG CT, hasWorkingGroup, CT WG6]
  • A. CT WG3
    CT WG3 is a 3GPP Core Network and Terminals working group responsible for standardizing protocols and interfaces related to core network signaling and services.
  • B. CT WG1
    CT WG1 is a 3GPP Core Network and Terminals working group responsible for specifying core network protocols and services, particularly in the control plane.
  • C. 3GPP CT6 chosen
    3GPP CT6 is a working subgroup within the 3GPP Core Network and Terminals (CT) group responsible for specifying protocols and codecs for multimedia telephony and related services.
  • D. IFIP Working Group 2.3
    IFIP Working Group 2.3 is an international expert group within the International Federation for Information Processing focused on the theory and practice of programming methodology and software development.
  • E. ISO Technical Committee 68
    ISO Technical Committee 68 is an international standards body responsible for developing and maintaining standards in the field of financial services.
  • 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_69c00834f6308190851b0abeddd8ed7e completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c029ac21ec81908d88ba72e966d7cb completed March 22, 2026, 5:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0a16ea7108190adb0756dac94c42c completed March 23, 2026, 2:11 a.m.
Created at: March 22, 2026, 3:50 p.m.