Triple
T21020155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Alabama |
E517783
|
entity |
| Predicate | capturedOrDestroyed |
P23911
|
FINISHED |
| Object | over 60 Union merchant vessels |
—
|
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: over 60 Union merchant vessels | Statement: [CSS Alabama, capturedOrDestroyed, over 60 Union merchant vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedOrDestroyed Context triple: [CSS Alabama, capturedOrDestroyed, over 60 Union merchant vessels]
-
A.
killedOrCaptured
Indicates that one entity has either killed or taken another entity into custody or control.
-
B.
fleetDestroyedBy
Indicates that a fleet was destroyed as a direct result of actions taken by another specified entity.
-
C.
capturedShip
chosen
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
D.
scuttledAfter
Indicates that one entity was deliberately sunk or rendered inoperable after the occurrence or completion of another specified event or action.
-
E.
capturedInWar
Indicates that one entity was taken prisoner or seized by another entity as a result of armed conflict or wartime actions.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5c905c8190ba2f9f82b6cd1648 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.