Triple
T540556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lomonosov Ridge |
E12617
|
entity |
| Predicate | minimumWaterDepthAboveCrest |
P15454
|
FINISHED |
| Object | about 954 m |
—
|
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: about 954 m | Statement: [Lomonosov Ridge, minimumWaterDepthAboveCrest, about 954 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumWaterDepthAboveCrest Context triple: [Lomonosov Ridge, minimumWaterDepthAboveCrest, about 954 m]
-
A.
lowestPoint
Indicates that one entity is the point with the minimum vertical position or value relative to another entity or within a specified context.
-
B.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
C.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
D.
oceanDepthBelow
Indicates that one location or point in the ocean is situated at a greater depth (deeper below the surface) than another.
-
E.
pressureAtBottom
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985feee481908184a39210feab95 |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b67c308190a1a225ab7c4b74c6 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49858abd48190bd4b002a93e4a908 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.