Triple
T14460374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobb Seamount |
E358566
|
entity |
| Predicate | summitDepthBelowSeaLevel |
P114737
|
FINISHED |
| Object | approximately 34 metres |
—
|
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: approximately 34 metres | Statement: [Cobb Seamount, summitDepthBelowSeaLevel, approximately 34 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitDepthBelowSeaLevel Context triple: [Cobb Seamount, summitDepthBelowSeaLevel, approximately 34 metres]
-
A.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
B.
summitElevationSouth
Indicates the elevation of the summit located on the southern side or in the southern part of a referenced geographic feature.
-
C.
summitLocatedIn
Indicates that a summit (mountain peak) is geographically situated within a specified area or region.
-
D.
isSummitOf
Indicates that one entity is the highest point or peak (summit) of another entity, such as a mountain or structure.
-
E.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:19 a.m.