Triple
T29685829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOIDES Resolution |
E751080
|
entity |
| Predicate | maximumWaterDepthDrillingCapability |
P42760
|
FINISHED |
| Object | about 8000 meters |
—
|
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 8000 meters | Statement: [JOIDES Resolution, maximumWaterDepthDrillingCapability, about 8000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumWaterDepthDrillingCapability Context triple: [JOIDES Resolution, maximumWaterDepthDrillingCapability, about 8000 meters]
-
A.
maximumWaterDepth
chosen
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
B.
maximumDiveDepth
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
C.
drillDepth
Indicates the measured or specified depth to which a drilling operation extends into a material or medium.
-
D.
minimumWaterDepth
Indicates the smallest water depth at which the related object, activity, or condition is valid, safe, or applicable.
-
E.
hasCaissonWaterDepth
Indicates the depth of water surrounding or contained within a caisson in a given 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 7:13 p.m.