Triple
T2841271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Pedestal |
E62472
|
entity |
| Predicate | survivingMerchantShips |
P24302
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Operation Pedestal, survivingMerchantShips, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivingMerchantShips Context triple: [Operation Pedestal, survivingMerchantShips, 5]
-
A.
survivingShipsOfFleet
chosen
Indicates the subset of ships from a given fleet that remain operational or undestroyed after a specific event or period.
-
B.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
C.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
D.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
E.
battleshipsDamaged
Indicates that one or more battleships have sustained damage, typically as a result of combat or hostile action.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf16d0c08190bb8de4a4160b4414 |
completed | March 7, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.