Triple
T22688233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LTE-WLAN Aggregation |
E560976
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object | 3GPP TS 36.331 |
—
|
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 TS 36.331 | Statement: [LTE-WLAN Aggregation, definedIn, 3GPP TS 36.331]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 36.331 Context triple: [LTE-WLAN Aggregation, definedIn, 3GPP TS 36.331]
-
A.
3GPP TS 36.331
chosen
3GPP TS 36.331 is a 3GPP technical specification that defines the Radio Resource Control (RRC) protocol for LTE (E-UTRA) networks.
-
B.
3GPP TS 25.331
3GPP TS 25.331 is a 3GPP technical specification that defines the Radio Resource Control (RRC) protocol for the UMTS (WCDMA) radio interface.
-
C.
3GPP TS 36.361
3GPP TS 36.361 is a technical specification that defines how LTE networks integrate and coordinate with Wi‑Fi (WLAN) to enhance mobile broadband performance.
-
D.
3GPP TS 36.321
3GPP TS 36.321 is a technical specification that defines the Medium Access Control (MAC) protocol for the LTE (E-UTRA) radio interface in 3GPP mobile networks.
-
E.
3GPP TS 33.310
3GPP TS 33.310 is a technical specification that defines security architecture and procedures for authentication, key management, and certificate handling in 3G mobile and LTE networks.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178983fc8819080aa00e45ff77952 |
completed | April 29, 2026, 3:18 a.m. |
Created at: April 17, 2026, 3:13 p.m.