Triple
T250754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bathyscaphe Trieste |
E5140
|
entity |
| Predicate | maximumOperatingDepth |
P1177
|
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: [bathyscaphe Trieste, maximumOperatingDepth, over 10,000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumOperatingDepth Context triple: [bathyscaphe Trieste, maximumOperatingDepth, over 10,000 metres]
-
A.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
B.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
-
C.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
D.
operatingTemperature
Indicates the range or specific value of temperature within which an entity is designed or allowed to function properly.
-
E.
hasMaximumDepth
chosen
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
- 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_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. |
Created at: Feb. 28, 2026, 2:54 a.m.