Triple
T21269634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMS core network |
E524220
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | 3GPP TS 29.228 |
—
|
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.228 | Statement: [IMS core network, definedIn, 3GPP TS 29.228]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.228 Context triple: [IMS core network, definedIn, 3GPP TS 29.228]
-
A.
3GPP TS 23.228
3GPP TS 23.228 is a core 3GPP technical specification that defines the system architecture and functional principles of the IP Multimedia Subsystem (IMS) for delivering multimedia services over mobile and IP networks.
-
B.
3GPP TS 29.281
3GPP TS 29.281 is a technical specification that defines the GPRS Tunnelling Protocol User Plane (GTP‑U) used for transporting user data in 3GPP mobile networks.
-
C.
3GPP TS 29.328
3GPP TS 29.328 is a 3rd Generation Partnership Project technical specification that defines key signaling and interface procedures for the IP Multimedia Subsystem (IMS) in mobile networks.
-
D.
3GPP TS 24.229
3GPP TS 24.229 is a core 3GPP specification that defines the signaling procedures and call control for IP Multimedia Subsystem (IMS) services over SIP in mobile and fixed networks.
-
E.
3GPP TS 29.272
3GPP TS 29.272 is a technical specification that defines the S6a/S6d Diameter-based interface between the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) and the Home Subscriber Server (HSS) in LTE/EPC 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.228 Target entity description: 3GPP TS 29.228 is a technical specification that defines the Cx and Dx interfaces and related procedures for subscriber and authentication data management in IP Multimedia Subsystem (IMS) networks.
-
A.
3GPP TS 23.228
3GPP TS 23.228 is a core 3GPP technical specification that defines the system architecture and functional principles of the IP Multimedia Subsystem (IMS) for delivering multimedia services over mobile and IP networks.
-
B.
3GPP TS 29.281
3GPP TS 29.281 is a technical specification that defines the GPRS Tunnelling Protocol User Plane (GTP‑U) used for transporting user data in 3GPP mobile networks.
-
C.
3GPP TS 29.328
3GPP TS 29.328 is a 3rd Generation Partnership Project technical specification that defines key signaling and interface procedures for the IP Multimedia Subsystem (IMS) in mobile networks.
-
D.
3GPP TS 24.229
3GPP TS 24.229 is a core 3GPP specification that defines the signaling procedures and call control for IP Multimedia Subsystem (IMS) services over SIP in mobile and fixed networks.
-
E.
3GPP TS 29.272
3GPP TS 29.272 is a technical specification that defines the S6a/S6d Diameter-based interface between the Mobility Management Entity (MME) or Serving GPRS Support Node (SGSN) and the Home Subscriber Server (HSS) in LTE/EPC 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.