Triple

T22062150
Position Surface form Disambiguated ID Type / Status
Subject 3GPP Release 5 E545179 entity
Predicate introducedFeatureType P101663 FINISHED
Object high-speed packet data 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: high-speed packet data | Statement: [3GPP Release 5, introducedFeatureType, high-speed packet data]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: introducedFeatureType
Context triple: [3GPP Release 5, introducedFeatureType, high-speed packet data]
  • A. introducedFeatureCategory
    Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
  • B. introducedFeatureFamily
    Indicates that an entity (such as a product or version) was responsible for first introducing a particular feature family.
  • C. introducedAsType
    Indicates that one entity is presented or identified to others as having a particular role, category, or type.
  • D. classIntroduced
    Indicates that a particular class (e.g., in a programming language or system) has been newly defined or made available within a given context or scope.
  • E. includesFeatureTypes chosen
    Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
  • 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_69e11e3377c48190890c17407b9527d6 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f1285e8c688190b701e417893cc148 completed April 28, 2026, 9:36 p.m.
PD Predicate disambiguation batch_69e6f643ca74819083e8ab78e843f243 completed April 21, 2026, 4 a.m.
Created at: April 16, 2026, 8:27 p.m.