Triple
T21533175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garganta del Diablo |
E531284
|
entity |
| Predicate | approximateDropType |
P144744
|
FINISHED |
| Object | multi-step vertical drop |
—
|
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: multi-step vertical drop | Statement: [Garganta del Diablo, approximateDropType, multi-step vertical drop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDropType Context triple: [Garganta del Diablo, approximateDropType, multi-step vertical drop]
-
A.
approximateDrop
Indicates an estimated or roughly calculated decrease in a quantity, value, or level rather than an exact measured drop.
-
B.
hasDropType
Indicates that an entity is associated with a specific type or category of drop (e.g., item, reward, or resource obtained).
-
C.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
D.
dropType
Indicates the manner or category of how something is dropped, released, or caused to fall.
-
E.
dragType
Indicates the manner or category of dragging interaction that occurs between entities.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0ae0e88190a6042effd93cd455 |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:27 p.m.