Triple
T3577921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHELON |
E75731
|
entity |
| Predicate | allegedCapabilities |
P17736
|
FINISHED |
| Object | global communications interception |
—
|
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: global communications interception | Statement: [ECHELON, allegedCapabilities, global communications interception]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedCapabilities Context triple: [ECHELON, allegedCapabilities, global communications interception]
-
A.
usedCapability
Indicates that an entity employed or exercised a particular capability, skill, or function in performing an action or achieving a result.
-
B.
consideredCapability
chosen
Indicates that something is regarded or evaluated as a potential capability of an entity.
-
C.
requiresCapability
Indicates that one entity depends on another entity possessing a specific capability in order for an action, function, or condition to be fulfilled.
-
D.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
E.
displayCapabilities
Indicates the set of functions, features, or behaviors that an entity is able to present or support in a given 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0dd3e048190a0c6666e13ead9cd |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.