Triple
T21226145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMF |
E523088
|
entity |
| Predicate | interfacesWith |
P12981
|
FINISHED |
| Object | gNB |
—
|
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: gNB | Statement: [AMF, interfacesWith, gNB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: gNB Context triple: [AMF, interfacesWith, gNB]
-
A.
gNB
chosen
gNB (next-generation Node B) is the 5G New Radio base station that provides radio access and connectivity between user equipment and the 5G core network.
-
B.
NG-RAN
NG-RAN is the 5G New Radio access network architecture specified by 3GPP, encompassing gNodeBs and their interfaces to the 5G core.
-
C.
eNodeB
eNodeB is the base station in LTE networks responsible for radio transmission, reception, and control functions between user devices and the core network.
-
D.
5G NR
5G NR is the global 5G wireless communication standard defined by 3GPP, designed to deliver significantly higher data rates, lower latency, and greater capacity than previous mobile network technologies.
-
E.
Home eNodeB Gateway
A Home eNodeB Gateway is a core network element in LTE that aggregates and manages traffic and signaling from multiple residential or enterprise femtocell base stations (Home eNodeBs) to the operator’s core network.
- 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_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.