Triple
T10665468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot Strait |
E251344
|
entity |
| Predicate | hasSubmarineTopography |
P37608
|
FINISHED |
| Object | shelf break and deep basin |
—
|
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: shelf break and deep basin | Statement: [Cabot Strait, hasSubmarineTopography, shelf break and deep basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubmarineTopography Context triple: [Cabot Strait, hasSubmarineTopography, shelf break and deep basin]
-
A.
hasBathymetricFeature
chosen
Indicates that one entity possesses, contains, or is associated with a specific underwater (seafloor) topographic feature.
-
B.
hasSeamount
Indicates that an entity possesses, contains, or is associated with a seamount (an underwater mountain).
-
C.
hasOceanTrench
Indicates that a body of water contains or is associated with a specific ocean trench within its area.
-
D.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
E.
hasSubsurfacePlatforms
Indicates that an entity includes or is equipped with platforms located below the surface or underground.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31f87748190bb44db8afa901763 |
completed | April 9, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.