Triple
T18426217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tara River Canyon |
E450145
|
entity |
| Predicate | rankingByDepth |
P1536
|
FINISHED |
| Object | one of the deepest river canyons in Europe |
—
|
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: one of the deepest river canyons in Europe | Statement: [Tara River Canyon, rankingByDepth, one of the deepest river canyons in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingByDepth Context triple: [Tara River Canyon, rankingByDepth, one of the deepest river canyons in Europe]
-
A.
depthRank
chosen
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
B.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
C.
rankEquivalent
Indicates that two entities hold the same rank or hierarchical level within a given ordering or classification system.
-
D.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
E.
rankByProminence
Indicates that entities are ordered or assigned a position based on their level of prominence or notability relative to one another.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b12606081908ea320fd8d5554c6 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:22 a.m.