Triple

T24005871
Position Surface form Disambiguated ID Type / Status
Subject 3GPP TS 48-series specifications E594383 entity
Predicate includes P1393 FINISHED
Object 3GPP TS 48.074
3GPP TS 48.074 is a technical specification within the 3GPP 48-series that defines aspects of the interface and protocols used in mobile telecommunications core network systems.
E1616737 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: 3GPP TS 48.074 | Statement: [3GPP TS 48-series specifications, includes, 3GPP TS 48.074]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: 3GPP TS 48.074
Triple: [3GPP TS 48-series specifications, includes, 3GPP TS 48.074]
Generated description
3GPP TS 48.074 is a technical specification within the 3GPP 48-series that defines aspects of the interface and protocols used in mobile telecommunications core network systems.

Provenance (5 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_69e288b9ecf08190b8c94a278f5674fe completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d4693a8c8190af2960c5832093f1 completed April 29, 2026, 9:50 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f964aaff0819081812563cc392709 completed May 21, 2026, 11:33 p.m.
NEDg Description generation batch_6a0f98412b7481908650f712a6dc3920 completed May 21, 2026, 11:41 p.m.
NED2 Entity disambiguation (via description) batch_6a0f998fc4148190bb12cfb35368557b completed May 21, 2026, 11:47 p.m.
Created at: April 17, 2026, 9:40 p.m.