Triple
T14460376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobb Seamount |
E358566
|
entity |
| Predicate | baseDepthBelowSeaLevel |
P36028
|
FINISHED |
| Object | approximately 3000 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 3000 metres | Statement: [Cobb Seamount, baseDepthBelowSeaLevel, approximately 3000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseDepthBelowSeaLevel Context triple: [Cobb Seamount, baseDepthBelowSeaLevel, approximately 3000 metres]
-
A.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
B.
isBelowSeaLevel
Indicates that one entity’s vertical position is lower than the standard sea level reference point.
-
C.
partlyBelowSeaLevel
Indicates that an entity’s elevation is such that some, but not all, of it lies below sea level.
-
D.
oceanDepthBelow
Indicates that one location or point in the ocean is situated at a greater depth (deeper below the surface) than another.
-
E.
seaDepth
chosen
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
- 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_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. |
Created at: April 10, 2026, 1:19 a.m.