Triple
T17272971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Emery |
E419310
|
entity |
| Predicate | testPurposeDetail |
P36935
|
FINISHED |
| Object | validation of warhead designs |
—
|
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: validation of warhead designs | Statement: [Operation Emery, testPurposeDetail, validation of warhead designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testPurposeDetail Context triple: [Operation Emery, testPurposeDetail, validation of warhead designs]
-
A.
testSeriesPurpose
chosen
Indicates that a test series is conducted with the specific purpose or objective of achieving a particular outcome or goal.
-
B.
testDetail
Indicates that there is specific, often granular information or attributes associated with a particular test or testing instance.
-
C.
servicePurpose
Indicates that one entity serves as the purpose, goal, or intended function for which another entity (typically a service) exists or is provided.
-
D.
expositionPurpose
Indicates that something (such as a text, speech, or display) serves the purpose of explaining, clarifying, or providing background information about a subject.
-
E.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4b023c8190b92df4015c14c3a8 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.