Triple
T16391881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSC 4-A |
E398071
|
entity |
| Predicate | typeOfOperationAuthorized |
P819
|
FINISHED |
| Object | black propaganda |
—
|
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: black propaganda | Statement: [NSC 4-A, typeOfOperationAuthorized, black propaganda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfOperationAuthorized Context triple: [NSC 4-A, typeOfOperationAuthorized, black propaganda]
-
A.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
B.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
-
C.
typeOfOperation
chosen
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
D.
typeOfAuthorization
Indicates the specific kind or category of authorization that applies to an action, resource, or relationship between entities.
-
E.
canOperateUnder
Indicates that one entity is permitted, able, or qualified to function, perform, or remain active within the conditions, authority, or environment defined by another 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326436ce881909f0f3899b8d931aa |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.