Triple
T64624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annual Threat Assessment |
E1284
|
entity |
| Predicate | publicVersion |
P3286
|
FINISHED |
| Object | unclassified report released to the public |
—
|
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: unclassified report released to the public | Statement: [Annual Threat Assessment, publicVersion, unclassified report released to the public]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicVersion Context triple: [Annual Threat Assessment, publicVersion, unclassified report released to the public]
-
A.
secondFullVersionReference
Indicates that an entity refers to a second complete or fully detailed version of another entity.
-
B.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
C.
firstFullVersionReference
Indicates that one entity serves as the initial complete or fully realized version to which another entity refers or is linked.
-
D.
releaseType
chosen
Indicates the kind or category of a release event or version associated with an entity.
-
E.
nextEdition
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a2516eda54819090f5c14384d4eab1 |
completed | Feb. 28, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69a24ea5c140819080409a968c8d2ce8 |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.