Triple
T28925094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeannette Arctic expedition |
E733618
|
entity |
| Predicate | shipSankIn |
P166021
|
FINISHED |
| Object | Arctic Ocean |
—
|
NE NERFINISHED |
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: Arctic Ocean | Statement: [Jeannette Arctic expedition, shipSankIn, Arctic Ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipSankIn Context triple: [Jeannette Arctic expedition, shipSankIn, Arctic Ocean]
-
A.
sunkBy
Indicates that one entity (typically a vessel or structure) was caused to sink or be destroyed in water by another entity.
-
B.
shipTypeSunk
Indicates that a particular type of ship has been sunk as a result of some event or action.
-
C.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
-
D.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
-
E.
wasSunkAs
Indicates that an entity met its end by being sunk in a specified role, context, or capacity.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 8:23 a.m.