Triple
T16015150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scenic Railway |
E388445
|
entity |
| Predicate | inclineType |
P111184
|
FINISHED |
| Object | steep incline |
—
|
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: steep incline | Statement: [Scenic Railway, inclineType, steep incline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inclineType Context triple: [Scenic Railway, inclineType, steep incline]
-
A.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
B.
inclinationClass
chosen
Indicates a categorization of something based on the type or degree of its inclination or tilt.
-
C.
slopeType
Indicates the classification of a slope based on its geometric or physical characteristics, such as steepness, shape, or orientation.
-
D.
hasSlopeRating
Indicates that something (typically a golf course or hole) is associated with a specific slope rating value that quantifies its relative difficulty for bogey golfers compared to scratch golfers.
-
E.
inclinationConstraint
Indicates a restriction or condition placed on the allowable angle or tilt between entities or components.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.