Triple
T22430138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 29.202 |
E554475
|
entity |
| Predicate | relatedToStandard |
P37
|
FINISHED |
| Object | 3GPP TS 29.198 |
—
|
NE NERFINISHED |
How this triple was built (3 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.198 | Statement: [3GPP TS 29.202, relatedToStandard, 3GPP TS 29.198]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.198 Context triple: [3GPP TS 29.202, relatedToStandard, 3GPP TS 29.198]
-
A.
3GPP TS 23.198
3GPP TS 23.198 is a 3rd Generation Partnership Project technical specification that defines the stage 2 architecture and procedures for Open Service Access (OSA) in mobile communication networks.
-
B.
3GPP TS 29.518
3GPP TS 29.518 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures between the Access and Mobility Management Function (AMF) and other 5G core network functions.
-
C.
3GPP TS 32.298
3GPP TS 32.298 is a 3rd Generation Partnership Project technical specification that defines charging data record (CDR) transfer and related charging management procedures for mobile telecommunications networks.
-
D.
3GPP TS 29.229
3GPP TS 29.229 is a technical specification that defines the Cx and Dx interfaces and related procedures for subscriber data management in the IP Multimedia Subsystem (IMS) core network.
-
E.
3GPP TS 32.299
3GPP TS 32.299 is a 3rd Generation Partnership Project technical specification that defines the Diameter-based charging interfaces and protocols used for offline and online charging in mobile networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.198 Target entity description: 3GPP TS 29.198 is a 3rd Generation Partnership Project technical specification that defines core network interfaces and protocols for IP Multimedia Subsystem (IMS) and related service control functions in mobile telecommunications.
-
A.
3GPP TS 23.198
3GPP TS 23.198 is a 3rd Generation Partnership Project technical specification that defines the stage 2 architecture and procedures for Open Service Access (OSA) in mobile communication networks.
-
B.
3GPP TS 29.518
3GPP TS 29.518 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures between the Access and Mobility Management Function (AMF) and other 5G core network functions.
-
C.
3GPP TS 32.298
3GPP TS 32.298 is a 3rd Generation Partnership Project technical specification that defines charging data record (CDR) transfer and related charging management procedures for mobile telecommunications networks.
-
D.
3GPP TS 29.229
3GPP TS 29.229 is a technical specification that defines the Cx and Dx interfaces and related procedures for subscriber data management in the IP Multimedia Subsystem (IMS) core network.
-
E.
3GPP TS 32.299
3GPP TS 32.299 is a 3rd Generation Partnership Project technical specification that defines the Diameter-based charging interfaces and protocols used for offline and online charging in mobile networks.
- F. None of above. chosen
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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
Created at: April 16, 2026, 8:47 p.m.