Triple
T32319211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallinn disaster |
E825726
|
entity |
| Predicate | numberOfShipsSunk |
P821
|
FINISHED |
| Object | over 60 |
—
|
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 | Statement: [Tallinn disaster, numberOfShipsSunk, over 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfShipsSunk Context triple: [Tallinn disaster, numberOfShipsSunk, over 60]
-
A.
firstShaftsSunk
Indicates that the initial mine shafts for a project or site have been excavated and established.
-
B.
tonnageSunk
Indicates the amount of a vessel’s weight or cargo capacity that has been destroyed or sunk, typically measured in tons.
-
C.
shipsSunkOrTotalLoss
chosen
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
D.
shipwrecksDestroyedIn
Indicates that one or more shipwrecks were destroyed within a specified location or during a particular event or time period.
-
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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01a819644c819094c58d083d525da0 |
completed | May 11, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_6a01a5dfd628819083c032d8cfd2e726 |
completed | May 11, 2026, 9:48 a.m. |
Created at: May 1, 2026, 12:46 a.m.