Triple
T33081102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-71 |
E846508
|
entity |
| Predicate | missionSecurityClassification |
P406
|
FINISHED |
| Object | Top Secret (U.S.) |
—
|
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 (U.S.) | Statement: [NROL-71, missionSecurityClassification, Top Secret (U.S.)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSecurityClassification Context triple: [NROL-71, missionSecurityClassification, Top Secret (U.S.)]
-
A.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
securityClassificationReason
Indicates the justification or basis for assigning a particular security classification to an entity or information.
-
C.
governmentClassification
Indicates that an entity is assigned a specific status or category according to a government’s official classification system.
-
D.
hasSecurityClass
Indicates that an entity is assigned to or associated with a particular security classification level.
-
E.
authorityResponsibleForClassification
Indicates that a particular authority or organization holds responsibility for determining and assigning the classification of an item or 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.