Triple
T3200243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RV Vityaz |
E67031
|
entity |
| Predicate | achievedDepthMeasurement |
P8582
|
FINISHED |
| Object | over 10,000 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: over 10,000 metres | Statement: [RV Vityaz, achievedDepthMeasurement, over 10,000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedDepthMeasurement Context triple: [RV Vityaz, achievedDepthMeasurement, over 10,000 metres]
-
A.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
B.
reachedDepth
chosen
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
C.
testDepth
Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
-
D.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
E.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada9ad4b1c8190bc6ad0f025f238c8 |
completed | March 8, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69ad9e05e4f48190adbe4366cdba2349 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.