Triple
T33111491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Ariadne |
E847343
|
entity |
| Predicate | sinkingBattle |
P18834
|
FINISHED |
| Object | Battle of Heligoland Bight |
—
|
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 Heligoland Bight | Statement: [SMS Ariadne, sinkingBattle, Battle of Heligoland Bight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sinkingBattle Context triple: [SMS Ariadne, sinkingBattle, Battle of Heligoland Bight]
-
A.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
shipAttacked
Indicates that one ship has carried out an attack against another ship.
-
C.
sinkingConflict
Indicates a situation where one entity’s decline, failure, or deterioration creates or intensifies a conflict with another entity.
-
D.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
E.
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.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6eb33648190b26122f53c88d8eb |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.