Triple
T20016047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotahuasi Canyon |
E494720
|
entity |
| Predicate | depthComparedTo |
P27142
|
FINISHED |
| Object | deeper than the Grand Canyon |
—
|
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: deeper than the Grand Canyon | Statement: [Cotahuasi Canyon, depthComparedTo, deeper than the Grand Canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthComparedTo Context triple: [Cotahuasi Canyon, depthComparedTo, deeper than the Grand Canyon]
-
A.
depthOrigin
Indicates the reference point or source location from which the depth of an object or region is measured.
-
B.
densityComparedTo
Indicates a comparison between the densities of two entities, specifying which is denser or how their densities relate.
-
C.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
D.
isDeeperThan
chosen
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
E.
depthClass
Indicates the categorical classification of an entity based on its depth or depth-related range.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623cb8188190b95913ffed895930 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.