Triple
T21226589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Slice Instance |
E523098
|
entity |
| Predicate | managedBy |
P86
|
FINISHED |
| Object | Network Slice Management Function |
—
|
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: Network Slice Management Function | Statement: [Network Slice Instance, managedBy, Network Slice Management Function]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Network Slice Management Function Context triple: [Network Slice Instance, managedBy, Network Slice Management Function]
-
A.
Network Slice Selection Function
The Network Slice Selection Function (NSSF) is a 5G core network function that determines and assigns the appropriate network slice for user equipment based on subscription, service requirements, and network policies.
-
B.
Network Slice Instance
A Network Slice Instance is a logically isolated, end-to-end 5G network partition tailored to specific service or customer requirements, providing dedicated resources and performance characteristics.
-
C.
Access and Mobility Management Function
The Access and Mobility Management Function (AMF) is a key 5G core network control-plane function responsible for user equipment registration, connection and mobility management, and access authentication.
-
D.
5G Core
5G Core is the cloud-native, service-based core network architecture that underpins 5G mobile systems, enabling advanced connectivity, slicing, and low-latency services.
-
E.
ONAP
ONAP (Open Network Automation Platform) is an open-source platform for real-time, policy-driven orchestration and automation of physical and virtual network functions, widely used by telecom operators to manage complex 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: Network Slice Management Function Target entity description: The Network Slice Management Function is a 5G network management component responsible for orchestrating, configuring, and monitoring network slice instances to meet specific service and performance requirements.
-
A.
Network Slice Selection Function
The Network Slice Selection Function (NSSF) is a 5G core network function that determines and assigns the appropriate network slice for user equipment based on subscription, service requirements, and network policies.
-
B.
Network Slice Instance
A Network Slice Instance is a logically isolated, end-to-end 5G network partition tailored to specific service or customer requirements, providing dedicated resources and performance characteristics.
-
C.
Access and Mobility Management Function
The Access and Mobility Management Function (AMF) is a key 5G core network control-plane function responsible for user equipment registration, connection and mobility management, and access authentication.
-
D.
5G Core
5G Core is the cloud-native, service-based core network architecture that underpins 5G mobile systems, enabling advanced connectivity, slicing, and low-latency services.
-
E.
ONAP
ONAP (Open Network Automation Platform) is an open-source platform for real-time, policy-driven orchestration and automation of physical and virtual network functions, widely used by telecom operators to manage complex 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ab3f6c819083e277ea1c33134e |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.