Triple
T18999689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skyline Drive (Alabama) |
E464914
|
entity |
| Predicate | stateHighestPointAccess |
P134072
|
FINISHED |
| Object | vicinity of Cheaha Mountain summit |
—
|
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: vicinity of Cheaha Mountain summit | Statement: [Skyline Drive (Alabama), stateHighestPointAccess, vicinity of Cheaha Mountain summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighestPointAccess Context triple: [Skyline Drive (Alabama), stateHighestPointAccess, vicinity of Cheaha Mountain summit]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
countryHighestPointAccess
Indicates that an entity has access to, or the ability to reach or utilize, the highest geographical point within a specified country.
-
C.
highestPointRegion
Indicates that one location is the highest point within a specified region.
-
D.
trailHighPointOf
Indicates that one location is the highest elevation point along a specified trail or route.
-
E.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d684d37c8190b975f04a47fa7b92 |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 12:01 p.m.