Triple
T2812719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Reconnaissance Regiment |
E54208
|
entity |
| Predicate | operationalSecrecy |
P13085
|
FINISHED |
| Object | covert |
—
|
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: covert | Statement: [Special Reconnaissance Regiment, operationalSecrecy, covert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalSecrecy Context triple: [Special Reconnaissance Regiment, operationalSecrecy, covert]
-
A.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
-
B.
securityOperation
Indicates an action or process carried out to protect, monitor, or defend assets, systems, or environments from threats or unauthorized activities.
-
C.
hasTypeOfSecrecy
chosen
Indicates that something is associated with a particular kind or level of secrecy.
-
D.
securityCodename
Indicates that an entity is assigned a specific codename used for security, confidentiality, or protective identification purposes.
-
E.
confidentialityProtectedBy
Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4a31d081909377044d5ff791b0 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.