Triple
T19310175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricketts Glen State Park |
E482942
|
entity |
| Predicate | hasHighestWaterfallHeight |
P47584
|
FINISHED |
| Object | 94 feet |
—
|
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: 94 feet | Statement: [Ricketts Glen State Park, hasHighestWaterfallHeight, 94 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestWaterfallHeight Context triple: [Ricketts Glen State Park, hasHighestWaterfallHeight, 94 feet]
-
A.
waterfallHeight
chosen
Indicates the vertical distance or drop in elevation from the top to the bottom of a waterfall.
-
B.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
C.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
D.
hasHighestPeaksOver
Indicates that one entity possesses mountain peaks that are higher in elevation than those of another entity.
-
E.
majorWaterfall
Indicates that a waterfall is of significant size, height, or volume relative to other waterfalls.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604cc62e08190b5ba5dfc44efdc5c |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.