Triple
T51841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSC-68 |
E1017
|
entity |
| Predicate | classifiedStatus |
P406
|
FINISHED |
| Object | Top Secret (at time of adoption) |
—
|
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 (at time of adoption) | Statement: [NSC-68, classifiedStatus, Top Secret (at time of adoption)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classifiedStatus Context triple: [NSC-68, classifiedStatus, Top Secret (at time of adoption)]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
C.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
D.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
E.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.