Triple

T21227052
Position Surface form Disambiguated ID Type / Status
Subject CT4 E523109 entity
Predicate relatedTo P37 FINISHED
Object 3GPP CT1 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: 3GPP CT1 | Statement: [CT4, relatedTo, 3GPP CT1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP CT1
Context triple: [CT4, relatedTo, 3GPP CT1]
  • A. 3GPP CT1 chosen
    3GPP CT1 is a working subgroup within the 3GPP Core Network and Terminals (CT) group responsible for specifying user equipment–core network signaling protocols and related aspects of mobile telecommunications standards.
  • B. 3GPP CT
    3GPP CT is the Core Network and Terminals Technical Specification Group within 3GPP responsible for standardizing core network protocols and terminal aspects of mobile telecommunications systems.
  • C. 3GPP CT2
    3GPP CT2 is a working group within the 3rd Generation Partnership Project responsible for developing core network protocols and services for mobile telecommunications.
  • D. 3GPP CT3
    3GPP CT3 is a working subgroup within the 3GPP Core Network and Terminals (CT) group responsible for specifying core network protocols and interfaces for mobile telecommunications systems.
  • E. 3GPP CT4
    3GPP CT4 is a working subgroup within the 3GPP Core Network and Terminals (CT) group responsible for developing and maintaining protocols for the mobile core network’s user-plane and related interfaces.
  • 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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734ac42a08190b95a24acf5f0779b completed April 21, 2026, 8:26 a.m.
Created at: April 16, 2026, 3:44 p.m.