Triple
T9499442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marksistskaya |
E229096
|
entity |
| Predicate | hasDepthBelowSurface |
P87151
|
FINISHED |
| Object | 60 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: 60 m | Statement: [Marksistskaya, hasDepthBelowSurface, 60 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDepthBelowSurface Context triple: [Marksistskaya, hasDepthBelowSurface, 60 m]
-
A.
depthBelowSurfaceInMeters
chosen
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
-
B.
isBelowSeaLevel
Indicates that one entity’s vertical position is lower than the standard sea level reference point.
-
C.
hasWaterDepthCategory
Indicates the classification of something based on the range or category of its water depth.
-
D.
depthRelativeToSeabed
Indicates the vertical distance of something measured relative to the seabed, typically how far above or below the seabed it is located.
-
E.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983a94c48190a7ddf95a953c4ecc |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.