Triple
T536843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger Deep |
E12344
|
entity |
| Predicate | depthMetresApprox |
P16570
|
FINISHED |
| Object | 10900 |
—
|
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: 10900 | Statement: [Challenger Deep, depthMetresApprox, 10900]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthMetresApprox Context triple: [Challenger Deep, depthMetresApprox, 10900]
-
A.
depth
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
B.
heightApproximateFeet
Indicates that one entity’s height is approximately equal to a specified value measured in feet.
-
C.
heightInCentimetres
Indicates the numerical value of an entity’s height measured in centimetres.
-
D.
hasAverageDepth
Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
-
E.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
- 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b51ff08190a39f4168fd9a7ddf |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.