Triple
T18905031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hochfirstschanze |
E462437
|
entity |
| Predicate | hasLandingSlope |
P25297
|
FINISHED |
| Object | steep landing hill |
—
|
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 landing hill | Statement: [Hochfirstschanze, hasLandingSlope, steep landing hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandingSlope Context triple: [Hochfirstschanze, hasLandingSlope, steep landing hill]
-
A.
hasSettlementOnSlopes
Indicates that a settlement is located on or extends across the slopes of a landform such as a hill or mountain.
-
B.
hasLandingCharacteristics
Indicates that an entity possesses specific attributes or features related to how it lands or is capable of landing.
-
C.
hasIncline
chosen
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
D.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
E.
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.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52c121c8190a2057b99c723694b |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.