Triple
T24769203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sliding Rock |
E619672
|
entity |
| Predicate | approximateDropHeight |
P38193
|
FINISHED |
| Object | about 6–7 feet into plunge pool |
—
|
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: about 6–7 feet into plunge pool | Statement: [Sliding Rock, approximateDropHeight, about 6–7 feet into plunge pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDropHeight Context triple: [Sliding Rock, approximateDropHeight, about 6–7 feet into plunge pool]
-
A.
approximateDrop
Indicates an estimated or roughly calculated decrease in a quantity, value, or level rather than an exact measured drop.
-
B.
approximateDropType
Indicates that one entity represents an estimated or inferred type or category of drop associated with another entity.
-
C.
approximateMaximumHeight
Indicates the estimated upper limit of an entity’s height, rather than an exact measured value.
-
D.
dropHeight
Indicates the vertical distance from which an object is released or allowed to fall.
-
E.
heightEstimate
chosen
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:29 a.m.