Triple
T23363027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proximity Services |
E593236
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 3GPP feature |
C44332
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: 3GPP feature Context triple: [Proximity Services, instanceOf, 3GPP feature]
-
A.
3GPP-defined functionality
chosen
3GPP-defined functionality encompasses standardized features, procedures, and interfaces specified by the 3rd Generation Partnership Project to ensure interoperability, performance, and compliance across mobile communication systems and networks.
-
B.
3GPP standardized parameter
A 3GPP standardized parameter is a formally defined technical value or setting specified by the 3rd Generation Partnership Project to ensure interoperability, performance, and compliance across mobile communication systems and equipment.
-
C.
mobile network feature set
A mobile network feature set is the collection of capabilities, services, and performance characteristics (such as voice, data, messaging, security, and quality-of-service options) provided by a mobile communication network to its users and connected devices.
-
D.
3GPP document type
A 3GPP document type is a categorized specification or report format defined by the 3rd Generation Partnership Project to standardize the structure, purpose, and lifecycle of technical documents related to mobile telecommunications.
-
E.
3GPP network node
A 3GPP network node is a standardized functional entity within a 3GPP-defined mobile network (such as LTE or 5G) that performs specific control, user-plane, or management tasks to enable communication services.
- F. None of above.
Provenance (1 batch)
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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:30 p.m.