Triple
T1076288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FISC |
E23845
|
entity |
| Predicate | confidentialityLevel |
P406
|
FINISHED |
| Object | highly classified |
—
|
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: highly classified | Statement: [FISC, confidentialityLevel, highly classified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confidentialityLevel Context triple: [FISC, confidentialityLevel, highly classified]
-
A.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
B.
protectionLevel
Indicates the degree or extent to which something is safeguarded against harm, risk, or unauthorized access.
-
C.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
-
D.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
E.
documentationLevel
Indicates the extent or thoroughness to which something is described, specified, or supported by written or recorded documentation.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b940d4848190930e73597afd1fcf |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.