Triple

T22061900
Position Surface form Disambiguated ID Type / Status
Subject JWICS E545173 entity
Predicate supportsClassificationLevel P66321 FINISHED
Object Top Secret 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: Top Secret | Statement: [JWICS, supportsClassificationLevel, Top Secret]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsClassificationLevel
Context triple: [JWICS, supportsClassificationLevel, Top Secret]
  • A. supportsClassificationUpTo chosen
    Indicates that one entity provides assistance, resources, or functionality enabling another entity to perform classification tasks up to a specified level, scope, or complexity.
  • B. classificationLevel
    Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
  • C. usesClassificationCriteria
    Indicates that one entity applies specific classification criteria to categorize, organize, or evaluate another entity.
  • D. securityClassification
    Indicates the level or category of security sensitivity or access restriction assigned to an entity.
  • E. recognizesLevel
    Indicates that one entity acknowledges, identifies, or is aware of the degree, rank, or intensity associated with another entity.
  • 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_69f1285d5e508190b3124a70fe55b32e 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.