Triple
T14038051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icebreaker Lenin |
E337763
|
entity |
| Predicate | accidents |
P20143
|
FINISHED |
| Object | experienced nuclear-related incidents during service |
—
|
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: experienced nuclear-related incidents during service | Statement: [Icebreaker Lenin, accidents, experienced nuclear-related incidents during service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accidents Context triple: [Icebreaker Lenin, accidents, experienced nuclear-related incidents during service]
-
A.
accident
chosen
Indicates an unintended, unforeseen event or mishap occurring, often resulting in damage, injury, or disruption.
-
B.
accidentType
Indicates the specific category or kind of accident associated with an event or incident.
-
C.
resultOfAccident
Indicates that something exists or occurs as a consequence or outcome of an accident.
-
D.
causedAccident
Indicates that one entity is responsible for bringing about or initiating an accident involving another entity or situation.
-
E.
fatalAccident
Indicates that an accident resulted in at least one death.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de30ee374081908b6b5e8f81dd90f2 |
completed | April 14, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.