Triple
T36299613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Říčky ski area |
E893470
|
entity |
| Predicate | hasSlopePreparation |
P185112
|
FINISHED |
| Object | machine grooming |
—
|
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: machine grooming | Statement: [Říčky ski area, hasSlopePreparation, machine grooming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSlopePreparation Context triple: [Říčky ski area, hasSlopePreparation, machine grooming]
-
A.
hasSlopeFeature
Indicates that an entity possesses or is characterized by a particular slope-related property or feature.
-
B.
hasSlopeProtection
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
-
C.
isOnSlopeOf
Indicates that one entity is located on the inclined surface or side of another entity, typically a sloping terrain or structure.
-
D.
hasIncline
Indicates that one entity possesses or exhibits a slope, tilt, or upward/downward angle relative to another reference.
-
E.
usesIntermediateSlope
Indicates that an entity employs or operates on a slope of intermediate steepness as part of its process or behavior.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb1d6b70819091227bd011734d19 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7ba6c27e081908868a2b50d1d603c |
completed | May 3, 2026, 9:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.