Triple
T536895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Challenger Deep |
E12344
|
entity |
| Predicate | isSuperlativeFor |
P2410
|
FINISHED |
| Object | maximum ocean depth on Earth |
—
|
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: maximum ocean depth on Earth | Statement: [Challenger Deep, isSuperlativeFor, maximum ocean depth on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuperlativeFor Context triple: [Challenger Deep, isSuperlativeFor, maximum ocean depth on Earth]
-
A.
superlative
chosen
Indicates that one entity possesses a property to the greatest or least degree when compared with all others in a given set.
-
B.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
C.
isStrongerThan
Indicates that one entity possesses greater physical power, force, or effectiveness than another entity.
-
D.
ranksAsSuperiorRace
Indicates that one group is regarded or treated as inherently superior in status, value, or worth compared to another group.
-
E.
isMaximumWhen
Indicates that a quantity or function reaches its greatest possible value under specified conditions or at a particular point.
- 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_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. |
Created at: March 1, 2026, 7:32 p.m.