Triple

T21264821
Position Surface form Disambiguated ID Type / Status
Subject 3GPP Release 4 E524098 entity
Predicate partOf P40 FINISHED
Object 3GPP 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 | Statement: [3GPP Release 4, partOf, 3GPP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 3GPP
Context triple: [3GPP Release 4, partOf, 3GPP]
  • A. 3GPP chosen
    3GPP is an international standards organization that develops technical specifications for mobile telecommunications technologies, including 3G, 4G LTE, and 5G.
  • B. 3GPP Technical Specifications
    3GPP Technical Specifications are standardized documents that define the technical requirements and protocols for mobile telecommunications systems, including 3G, 4G, and 5G networks.
  • C. 3GPP RAN
    3GPP RAN is the standards group within 3GPP responsible for specifying the radio access network technologies and protocols used in mobile communication systems such as LTE and 5G.
  • D. 3GPP SA
    3GPP SA (Service and System Aspects) is the working group within the 3rd Generation Partnership Project responsible for overall system architecture, service requirements, and cross-domain coordination for mobile communication standards.
  • E. 3GPP Working Groups
    3GPP Working Groups are specialized expert teams within the 3rd Generation Partnership Project responsible for developing and maintaining technical specifications and reports for mobile telecommunications standards.
  • 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_69e0b5156d7881909bd4f83676590715 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735ea74e0819099d724de95996c90 completed April 21, 2026, 8:31 a.m.
Created at: April 16, 2026, 4 p.m.