Triple

T9613171
Position Surface form Disambiguated ID Type / Status
Subject Special Telecommunications Service E232152 entity
Predicate securityClassificationScope P81364 FINISHED
Object state secret communications 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: state secret communications | Statement: [Special Telecommunications Service, securityClassificationScope, state secret communications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: securityClassificationScope
Context triple: [Special Telecommunications Service, securityClassificationScope, state secret communications]
  • A. securityClassification
    Indicates the level or category of security sensitivity or access restriction assigned to an entity.
  • B. governmentClassification
    Indicates that an entity is assigned a specific status or category according to a government’s official classification system.
  • C. securityGranularity
    Indicates the level of detail or specificity at which security controls, permissions, or protections are defined and applied within a system or context.
  • D. classificationLevel
    Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
  • E. securityScope chosen
    Indicates the range or extent of protection, permissions, or access control that applies within a given security context.
  • 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_69ca8485a90c819094fe40b42fde9d70 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9a8885f88190887843e0fb32a5f3 completed April 1, 2026, 10:22 p.m.
PD Predicate disambiguation batch_69ccd5a6fd2481908efd131e207b8143 completed April 1, 2026, 8:21 a.m.
Created at: March 30, 2026, 8:09 p.m.