Triple
T33357086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endurance (ship) |
E854101
|
entity |
| Predicate | becameTrappedInIce |
P155587
|
FINISHED |
| Object | 1915-01-18 |
—
|
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: 1915-01-18 | Statement: [Endurance (ship), becameTrappedInIce, 1915-01-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameTrappedInIce Context triple: [Endurance (ship), becameTrappedInIce, 1915-01-18]
-
A.
crushedByIce
Indicates that an entity is forcibly broken, flattened, or severely damaged as a result of pressure or impact from ice.
-
B.
shipTrappedInIceDate
chosen
Indicates the date on which a ship became immobilized or trapped in ice.
-
C.
trappedIn
Indicates that one entity is confined or caught within another entity or bounded space, unable to leave freely.
-
D.
trappedWith
Indicates that two or more entities are confined together in the same restricted space or situation, unable to leave independently.
-
E.
requiresGlacierTravel
Indicates that performing the activity or reaching the objective necessitates traveling over glacier terrain, typically involving glacier-specific skills and equipment.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:34 a.m.