Triple
T5330101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spruce Knob–Seneca Rocks National Recreation Area |
E123283
|
entity |
| Predicate | hasPeakElevation |
P28306
|
FINISHED |
| Object | 4863 ft |
—
|
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: 4863 ft | Statement: [Spruce Knob–Seneca Rocks National Recreation Area, hasPeakElevation, 4863 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeakElevation Context triple: [Spruce Knob–Seneca Rocks National Recreation Area, hasPeakElevation, 4863 ft]
-
A.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
B.
hasAverageElevation
chosen
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
C.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
-
D.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
E.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
- 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_69bd46477f9081909d242a327d749466 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd859552d8819080758bdd7c43c66a |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.