Triple
T33110933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Leipzig |
E847328
|
entity |
| Predicate | scuttlingAttempt |
P175580
|
FINISHED |
| Object | crew attempted to scuttle before sinking |
—
|
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: crew attempted to scuttle before sinking | Statement: [SMS Leipzig, scuttlingAttempt, crew attempted to scuttle before sinking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scuttlingAttempt Context triple: [SMS Leipzig, scuttlingAttempt, crew attempted to scuttle before sinking]
-
A.
scuttledAfter
Indicates that one entity was deliberately sunk or rendered inoperable after the occurrence or completion of another specified event or action.
-
B.
scuttlingOrderedBy
Indicates that one entity ordered, directed, or authorized the scuttling (intentional sinking or disabling) of another entity.
-
C.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
D.
reasonForScuttling
Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
-
E.
shipAttacked
Indicates that one ship has carried out an attack against another ship.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6d30b9e048190b0982e30b7fdfa3c |
completed | May 3, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:27 a.m.