Triple
T21226447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nudm |
E523095
|
entity |
| Predicate | definedInStandard |
P1371
|
FINISHED |
| Object | 3GPP TS 29.503 |
—
|
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: 3GPP TS 29.503 | Statement: [Nudm, definedInStandard, 3GPP TS 29.503]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 29.503 Context triple: [Nudm, definedInStandard, 3GPP TS 29.503]
-
A.
3GPP TS 29.503
chosen
3GPP TS 29.503 is a technical specification defining core network interfaces and procedures within the 3GPP 29-series for mobile telecommunications systems.
-
B.
3GPP TS 24.503
3GPP TS 24.503 is a technical specification that defines the Non-Access Stratum (NAS) signaling procedures for 5G system (5GS) mobile devices and networks.
-
C.
3GPP TS 29.502
3GPP TS 29.502 is a technical specification that defines the service-based interface procedures and signaling for the 5G core network in the 3GPP system architecture.
-
D.
3GPP TS 29.501
3GPP TS 29.501 is a technical specification that defines the system architecture and core network signaling interfaces for 5G networks within the 3GPP standards framework.
-
E.
3GPP TS 29.510
3GPP TS 29.510 is a 3rd Generation Partnership Project technical specification that defines the service-based interface and procedures for the Network Repository Function (NRF) within 5G core networks.
- 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.