Triple
T250725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bathyscaphe Trieste |
E5140
|
entity |
| Predicate | reachedDepth |
P8582
|
FINISHED |
| Object | about 10,911 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: about 10,911 metres | Statement: [bathyscaphe Trieste, reachedDepth, about 10,911 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedDepth Context triple: [bathyscaphe Trieste, reachedDepth, about 10,911 metres]
-
A.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
B.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
C.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.