Triple
T35958950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Kamloops wreck |
E1039943
|
entity |
| Predicate | locatedOnSeabedFeature |
P137559
|
FINISHED |
| Object | lake bottom of Lake Superior |
—
|
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: lake bottom of Lake Superior | Statement: [SS Kamloops wreck, locatedOnSeabedFeature, lake bottom of Lake Superior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSeabedFeature Context triple: [SS Kamloops wreck, locatedOnSeabedFeature, lake bottom of Lake Superior]
-
A.
partOfUnderseaFeature
Indicates that one undersea feature is a component or subdivision of a larger undersea feature.
-
B.
seaBedFeature
chosen
Indicates that an entity is a physical feature or formation located on or forming part of the seabed.
-
C.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
D.
sideRestingOnSeafloor
Indicates that one side of an object is in direct contact with and supported by the seafloor.
-
E.
isSubseaBasinOf
Indicates that a geological basin is located beneath the sea and is part of, or contained within, a larger marine or oceanic region.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.