Triple

T23871140
Position Surface form Disambiguated ID Type / Status
Subject Service and System Aspects Working Group 4 E592731 entity
Predicate usesStandardizationBody P1251 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: [Service and System Aspects Working Group 4, usesStandardizationBody, 3GPP]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesStandardizationBody
Context triple: [Service and System Aspects Working Group 4, usesStandardizationBody, 3GPP]
  • A. hasStandardizationBody chosen
    Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
  • B. usesStandard
    Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
  • C. isStandard
    Indicates that something conforms to an established norm, specification, or commonly accepted rule.
  • D. isStandardOf
    Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
  • E. usesBody
    Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
  • 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_69e25d23a5c88190ae3999c70ca15e08 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1cbfe1f948190ad2c0d5bbe0c7240 completed April 29, 2026, 9:14 a.m.
PD Predicate disambiguation batch_69f1614a65a88190bde1efb368a151e4 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:14 p.m.