Triple
T17252275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lookout Mountain (Colorado) |
E418784
|
entity |
| Predicate | roadTypeOnSlopes |
P1777
|
FINISHED |
| Object | scenic mountain road |
—
|
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: scenic mountain road | Statement: [Lookout Mountain (Colorado), roadTypeOnSlopes, scenic mountain road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeOnSlopes Context triple: [Lookout Mountain (Colorado), roadTypeOnSlopes, scenic mountain road]
-
A.
roadType
Indicates the classification or category of a road based on its functional or physical characteristics.
-
B.
appliesToRoadType
Indicates that a rule, condition, or attribute is specifically relevant or valid for a particular type or category of road.
-
C.
roadPassType
Indicates the type or category of permission or authorization required to use or pass along a particular road or route.
-
D.
hillType
Indicates the specific classification or category of a hill based on its form, characteristics, or context.
-
E.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e694f788190a1c86e95264ed2fe |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.