Triple
T34247000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winfield Scott |
E878623
|
entity |
| Predicate | proposedStrategy |
P107577
|
FINISHED |
| Object | Union blockade of the Confederacy |
—
|
NE NERFINISHED |
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: Union blockade of the Confederacy | Statement: [Winfield Scott, proposedStrategy, Union blockade of the Confederacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedStrategy Context triple: [Winfield Scott, proposedStrategy, Union blockade of the Confederacy]
-
A.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
claimedStrategy
Indicates that an entity asserts or reports using a particular strategy, approach, or plan.
-
C.
strategizesFor
Indicates that one entity plans or devises strategies on behalf of, or in support of, another entity.
-
D.
hasProposed
chosen
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
E.
laterStrategy
Indicates that one strategy or plan occurs or is implemented after another strategy in time.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:56 a.m.