Triple
T3547080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirshov Ridge |
E75021
|
entity |
| Predicate | maximumWaterDepthAbove |
P15453
|
FINISHED |
| Object | approximately 2000–3000 meters |
—
|
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 2000–3000 meters | Statement: [Shirshov Ridge, maximumWaterDepthAbove, approximately 2000–3000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumWaterDepthAbove Context triple: [Shirshov Ridge, maximumWaterDepthAbove, approximately 2000–3000 meters]
-
A.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
B.
minimumWaterDepthAboveCrest
Indicates the smallest required depth of water that must be maintained above the crest level of a structure or feature.
-
C.
lakeMaximumDepth
Indicates the greatest recorded vertical distance from the lake’s surface to its deepest point.
-
D.
maximumHeightAboveSeafloor
chosen
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
-
E.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.