Triple
T9101034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospekt Vernadskogo |
E218152
|
entity |
| Predicate | depthBelowSurfaceInMeters |
P87151
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Prospekt Vernadskogo, depthBelowSurfaceInMeters, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthBelowSurfaceInMeters Context triple: [Prospekt Vernadskogo, depthBelowSurfaceInMeters, 8]
-
A.
depthRelativeToSeabed
Indicates the vertical distance of something measured relative to the seabed, typically how far above or below the seabed it is located.
-
B.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
C.
riverbedDepth
Indicates the depth or vertical distance from the water surface to the bottom of a river at a given location or time.
-
D.
seaDepth
Indicates the measured vertical distance from the sea surface down to the seafloor at a given location.
-
E.
oceanDepthBelow
Indicates that one location or point in the ocean is situated at a greater depth (deeper below the surface) than another.
- 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_69ca83d9844081908e561e367fda6d45 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc9711babc8190a336812dd08d9c73 |
completed | April 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69cc65fc7f408190a5846e29ab3b97e5 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:15 p.m.