Triple
T28374500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project 523 |
E718720
|
entity |
| Predicate | reasonForConfidentiality |
P47269
|
FINISHED |
| Object | military and strategic importance |
—
|
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: military and strategic importance | Statement: [Project 523, reasonForConfidentiality, military and strategic importance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForConfidentiality Context triple: [Project 523, reasonForConfidentiality, military and strategic importance]
-
A.
confidentialityProtectedBy
Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
-
B.
visibilityReason
Indicates the reason or cause for why something is visible or has become visible in a given context.
-
C.
isConfidential
Indicates that the associated information, communication, or resource is intended to be kept secret and restricted to authorized parties only.
-
D.
confidentialityStatusAtTheTime
Indicates the level or state of confidentiality that applied to something at a specific point in time.
-
E.
reasonForSuppression
chosen
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 1:02 a.m.