Triple
T306529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAUD Report |
E6314
|
entity |
| Predicate | confidentialityStatus |
P406
|
FINISHED |
| Object | declassified (post-war) |
—
|
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: declassified (post-war) | Statement: [MAUD Report, confidentialityStatus, declassified (post-war)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confidentialityStatus Context triple: [MAUD Report, confidentialityStatus, declassified (post-war)]
-
A.
isWithheldBy
Indicates that something (such as information, resources, or permission) is deliberately not given, released, or made available by a particular entity.
-
B.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
C.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
-
D.
securityClassification
chosen
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
-
E.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
- 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_69a2e79230508190b912ecb555aae17e |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea313be88190b4441f3ea41a99e2 |
completed | Feb. 28, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69a2e93db11881909b07ba5e76d91feb |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.