Triple
T22430097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP TS 33-series |
E554474
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | 3GPP TS 33.126 |
—
|
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 33.126 | Statement: [3GPP TS 33-series, includes, 3GPP TS 33.126]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 33.126 Context triple: [3GPP TS 33-series, includes, 3GPP TS 33.126]
-
A.
3GPP TS 33.106
3GPP TS 33.106 is a technical specification within the 3GPP security series that defines security requirements and mechanisms for mobile telecommunications systems.
-
B.
3GPP TS 32.260
3GPP TS 32.260 is a technical specification within the 3GPP 32-series that defines aspects of telecommunications network management and operations.
-
C.
3GPP TS 32.106
3GPP TS 32.106 is a technical specification that defines aspects of the telecommunications management network within the 3GPP standards framework, focusing on operations, administration, and maintenance of mobile networks.
-
D.
3GPP TS 33.512
3GPP TS 33.512 is a technical specification within the 3GPP security series that defines security mechanisms and requirements for specific aspects of mobile telecommunications networks.
-
E.
3GPP TS 33.102
3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) 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 33.126 Target entity description: 3GPP TS 33.126 is a technical specification within the 3GPP security series that defines security requirements and mechanisms for mobile telecommunications systems.
-
A.
3GPP TS 33.106
3GPP TS 33.106 is a technical specification within the 3GPP security series that defines security requirements and mechanisms for mobile telecommunications systems.
-
B.
3GPP TS 32.260
3GPP TS 32.260 is a technical specification within the 3GPP 32-series that defines aspects of telecommunications network management and operations.
-
C.
3GPP TS 32.106
3GPP TS 32.106 is a technical specification that defines aspects of the telecommunications management network within the 3GPP standards framework, focusing on operations, administration, and maintenance of mobile networks.
-
D.
3GPP TS 33.512
3GPP TS 33.512 is a technical specification within the 3GPP security series that defines security mechanisms and requirements for specific aspects of mobile telecommunications networks.
-
E.
3GPP TS 33.102
3GPP TS 33.102 is a technical specification that defines the security architecture and mechanisms for 3G (UMTS) 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.