Triple
T8815423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treadstone |
E209763
|
entity |
| Predicate | operationalSecrecyLevel |
P13085
|
FINISHED |
| Object | black budget |
—
|
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: black budget | Statement: [Treadstone, operationalSecrecyLevel, black budget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalSecrecyLevel Context triple: [Treadstone, operationalSecrecyLevel, black budget]
-
A.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
securityLevelDetail
Indicates the specific classification or degree of security associated with an entity, often including nuanced or descriptive information about its protection level.
-
C.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
D.
hasTypeOfSecrecy
chosen
Indicates that something is associated with a particular kind or level of secrecy.
-
E.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given 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_69ca8363f3308190a47e3f1ebd51f613 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5ff2ff248190bafcafe8b3860e53 |
completed | March 31, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:45 p.m.