Triple

T21225666
Position Surface form Disambiguated ID Type / Status
Subject GPRS Tunnelling Protocol User Plane E523078 entity
Predicate roleInLTE P57746 FINISHED
Object transport of user data between eNodeB and SGW LITERAL 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: transport of user data between eNodeB and SGW | Statement: [GPRS Tunnelling Protocol User Plane, roleInLTE, transport of user data between eNodeB and SGW]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInLTE
Context triple: [GPRS Tunnelling Protocol User Plane, roleInLTE, transport of user data between eNodeB and SGW]
  • A. roleIn3GPP
    Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
  • B. roleInProtocolStack chosen
    Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
  • C. roleWithLAT
    Indicates a relationship where an entity holds or is associated with a specific role that is characterized or constrained by a particular location, attribute, or type (LAT).
  • D. hasTelecommunicationsRole
    Indicates that an entity holds or performs a specific function, position, or responsibility within the field of telecommunications.
  • E. roleInLap
    Indicates the specific function or position an entity holds during a particular lap within a sequence of laps.
  • F. None of above.

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_69e0b512ad94819087942b2ed925185f completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734ab3f6c819083e277ea1c33134e completed April 21, 2026, 8:26 a.m.
PD Predicate disambiguation batch_69e5f60e1a888190ba75e2e900270a4e completed April 20, 2026, 9:46 a.m.
Created at: April 16, 2026, 3:44 p.m.