Triple
T21226183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMF |
E523088
|
entity |
| Predicate | roleIn5G |
P23652
|
FINISHED |
| Object | central access and mobility control entity |
—
|
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: central access and mobility control entity | Statement: [AMF, roleIn5G, central access and mobility control entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleIn5G Context triple: [AMF, roleIn5G, central access and mobility control entity]
-
A.
roleIn3GPP
chosen
Indicates that an entity holds a specific role or function within the context of 3GPP (Third Generation Partnership Project) standards or activities.
-
B.
roleInProtocolStack
Indicates the specific function or position an entity occupies within a layered communication or protocol stack.
-
C.
roleInGateway
Indicates that an entity holds a specific function or responsibility within a particular gateway system or process.
-
D.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
E.
hasTelecommunicationsRole
Indicates that an entity holds or performs a specific function, position, or responsibility within the field of telecommunications.
- 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.