Triple
T3345883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anaconda Plan |
E70372
|
entity |
| Predicate | blockadeType |
P47357
|
FINISHED |
| Object | naval blockade |
—
|
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: naval blockade | Statement: [Anaconda Plan, blockadeType, naval blockade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockadeType Context triple: [Anaconda Plan, blockadeType, naval blockade]
-
A.
blockadedIn
Indicates that one entity is prevented or obstructed by another from entering, leaving, or accessing a particular place or resource.
-
B.
blockadeImpact
Indicates the effect or consequences that a blockade has on the targeted entities or systems.
-
C.
navalBaseType
Indicates the specific category or classification of a naval base in terms of its role, function, or operational characteristics.
-
D.
fortType
Indicates the specific kind or classification of a fort associated with an entity.
-
E.
coastalDefense
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
- F. None of above. chosen
Provenance (4 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f36c74819093ef2c74a46c2351 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.