Triple
T27227382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronan |
E682053
|
entity |
| Predicate | sinkingEvent |
P18834
|
FINISHED |
| Object | Battle of Öland |
—
|
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: Battle of Öland | Statement: [Kronan, sinkingEvent, Battle of Öland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingEvent Context triple: [Kronan, sinkingEvent, Battle of Öland]
-
A.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
-
B.
sankOn
Indicates that one entity moved downward and became submerged or lower in level relative to another entity or reference point.
-
C.
shipwreckEvent
Indicates an event in which a ship is destroyed, stranded, or severely damaged, typically resulting in loss or abandonment at sea or near a shoreline.
-
D.
sunkDuring
chosen
Indicates that one entity was sunk in the course of, or as a result of, the event or time period represented by another entity.
-
E.
sinkingConsequence
Indicates the outcome or effect that results from something sinking.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264bcdc08190b0860b3015aac6c6 |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:45 a.m.