Triple
T17421902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trümmelbach Falls |
E423636
|
entity |
| Predicate | approximateHeightDrop |
P42279
|
FINISHED |
| Object | over 140 meters |
—
|
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: over 140 meters | Statement: [Trümmelbach Falls, approximateHeightDrop, over 140 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateHeightDrop Context triple: [Trümmelbach Falls, approximateHeightDrop, over 140 meters]
-
A.
dropHeight
chosen
Indicates the vertical distance from which an object is released or allowed to fall.
-
B.
verticalDrop_ft
Indicates the vertical distance, measured in feet, that one entity drops or falls relative to another reference level.
-
C.
approximateDrop
Indicates an estimated or roughly calculated decrease in a quantity, value, or level rather than an exact measured drop.
-
D.
elevationApproxMeters
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
E.
hasApproxElevationFeet
Indicates that an entity is associated with an elevation value measured in feet that is approximate rather than exact.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44237f2cc819083ca0e7e00d828fb |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.