Triple
T34287579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prize Cases |
E879781
|
entity |
| Predicate | upheldAction |
P1123
|
FINISHED |
| Object | Union naval blockade of Confederate ports |
—
|
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: Union naval blockade of Confederate ports | Statement: [Prize Cases, upheldAction, Union naval blockade of Confederate ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upheldAction Context triple: [Prize Cases, upheldAction, Union naval blockade of Confederate ports]
-
A.
upheldBy
chosen
Indicates that one entity is supported, maintained, or validated by another, often through approval, enforcement, or confirmation of its validity.
-
B.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
C.
raisedUnder
Indicates that one entity was brought up, nurtured, or reared under the care, authority, or influence of another entity.
-
D.
mayUphold
Indicates that an authority or decision-maker has the option or power to confirm, maintain, or support a prior decision, rule, or judgment.
-
E.
upheldYear
Indicates the year in which a decision, ruling, or status was confirmed and maintained rather than overturned.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.