Triple
T25112793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anglo-American naval warfare |
E629043
|
entity |
| Predicate | involvesStrategy |
P164973
|
FINISHED |
| Object | 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: blockade | Statement: [Anglo-American naval warfare, involvesStrategy, blockade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStrategy Context triple: [Anglo-American naval warfare, involvesStrategy, blockade]
-
A.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
finalPlanInvolves
Indicates that a completed or chosen plan includes or incorporates a particular element, action, or component as part of its structure or execution.
-
C.
involvesPrinciple
Indicates that an action, process, or situation is based on, governed by, or makes essential use of a particular principle.
-
D.
mayBeInvolvedIn
Indicates that an entity has a possible, but not certain, participation or role in a particular event, activity, or situation.
-
E.
involvesLeader
Indicates that the relationship or action includes or is carried out by an entity serving in a leadership role.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 18, 2026, 6:27 a.m.