Triple
T29685830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOIDES Resolution |
E751080
|
entity |
| Predicate | maximumDrillingDepthBelowSeafloor |
P180334
|
FINISHED |
| Object | about 2000 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 2000 meters | Statement: [JOIDES Resolution, maximumDrillingDepthBelowSeafloor, about 2000 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDrillingDepthBelowSeafloor Context triple: [JOIDES Resolution, maximumDrillingDepthBelowSeafloor, about 2000 meters]
-
A.
maximumHeightAboveSeafloor
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
-
B.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
C.
maximumDiveDepth
Indicates the greatest depth below the surface that an entity is capable of or allowed to dive.
-
D.
designedTargetDepthInKilometers
Indicates the intended or planned depth, measured in kilometers, that something is designed to reach or operate at.
-
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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 28, 2026, 7:13 p.m.