Triple
T3717832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Window (radar countermeasures) |
E81572
|
entity |
| Predicate | reasonForSecrecy |
P47269
|
FINISHED |
| Object | fear enemy would copy the technique |
—
|
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: fear enemy would copy the technique | Statement: [Window (radar countermeasures), reasonForSecrecy, fear enemy would copy the technique]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForSecrecy Context triple: [Window (radar countermeasures), reasonForSecrecy, fear enemy would copy the technique]
-
A.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
C.
penaltyForRevealingSecrets
Indicates that an entity incurs a punishment or negative consequence as a result of disclosing confidential or secret information.
-
D.
protectionReason
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
-
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_69ad8b1a81588190b3f27a5483bb610e |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adca984844819087a2f6b20d2f19e7 |
completed | March 8, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.