Triple
T14616114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | icebreaker Chelyuskin |
E343089
|
entity |
| Predicate | crewRescued |
P115060
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [icebreaker Chelyuskin, crewRescued, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRescued Context triple: [icebreaker Chelyuskin, crewRescued, true]
-
A.
airmenRescuedFrom
Indicates that one or more airmen were saved or extracted from a particular person, place, situation, or danger.
-
B.
usedMeansToRescue
Indicates that one entity employed a particular method, tool, or means in order to carry out a rescue.
-
C.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
D.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
E.
allegedRescueEvent
Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.