Triple
T6305299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3GPP RAN |
E141359
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | E-UTRAN |
E123442
|
NE FINISHED |
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: E-UTRAN | Statement: [3GPP RAN, defines, E-UTRAN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: E-UTRAN Context triple: [3GPP RAN, defines, E-UTRAN]
-
A.
E-UTRAN
chosen
E-UTRAN is the LTE mobile network’s air-interface subsystem that connects user devices to the core network via evolved base stations (eNodeBs).
-
B.
eNodeB
eNodeB is the base station in LTE networks responsible for radio transmission, reception, and control functions between user devices and the core network.
-
C.
UTRAN
UTRAN (UMTS Terrestrial Radio Access Network) is the 3G radio access network architecture used in UMTS mobile communication systems to connect user devices to the core network.
-
D.
LTE
LTE (Long Term Evolution) is a high-speed wireless communication standard for mobile devices and data terminals, widely used as the foundation of 4G cellular networks.
-
E.
Evolved Packet Core
Evolved Packet Core is the 4G LTE mobile network architecture responsible for managing data connectivity, mobility, and services between user devices and external IP networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06479acec819090306a155a03b774 |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e44527488190b3d605e917c8dfb2 |
completed | March 27, 2026, 1:58 a.m. |
Created at: March 22, 2026, 4:28 p.m.