Triple
T23475509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TS 26-series |
E570250
|
entity |
| Predicate | includes |
P1393
|
FINISHED |
| Object | 3GPP TS 26.071 |
—
|
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 26.071 | Statement: [TS 26-series, includes, 3GPP TS 26.071]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 3GPP TS 26.071 Context triple: [TS 26-series, includes, 3GPP TS 26.071]
-
A.
3GPP TS 26.071
chosen
3GPP TS 26.071 is a technical specification that defines the Adaptive Multi-Rate (AMR) speech codec for use in 3G and later mobile communication systems.
-
B.
3GPP TS 44.071
3GPP TS 44.071 is a technical specification within the 3GPP 44-series that defines aspects of the GSM/GERAN radio interface for mobile communication systems.
-
C.
3GPP TS 22.071
3GPP TS 22.071 is a technical specification that defines the service requirements and features for location services (LCS) in mobile communication systems.
-
D.
3GPP TS 26.073
3GPP TS 26.073 is a technical specification within the 3GPP 26-series that defines aspects of audio and multimedia codecs used in mobile communication systems.
-
E.
3GPP TS 27.007
3GPP TS 27.007 is a technical specification that defines AT command sets and control procedures for 3GPP mobile equipment and terminals.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a704e2a48190acb55f77a2124412 |
completed | April 29, 2026, 6:36 a.m. |
Created at: April 17, 2026, 6:01 p.m.