Triple
T28925093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeannette Arctic expedition |
E733618
|
entity |
| Predicate | shipCrushedBy |
P4687
|
FINISHED |
| Object | ice |
—
|
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: ice | Statement: [Jeannette Arctic expedition, shipCrushedBy, ice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipCrushedBy Context triple: [Jeannette Arctic expedition, shipCrushedBy, ice]
-
A.
sunkBy
chosen
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
shipwreckType
Indicates the specific kind or classification of a shipwreck associated with an entity.
-
C.
shipwreck
Indicates that a vessel has been destroyed, stranded, or severely damaged, typically at sea or near a shoreline.
-
D.
shipwreckEvent
Indicates an event in which a ship is destroyed, stranded, or severely damaged, typically resulting in loss or abandonment at sea or near a shoreline.
-
E.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b1de60c8190aab3a7c29185f1fa |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:23 a.m.