Triple
T34864919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veľký Rozsutec |
E1004983
|
entity |
| Predicate | touristMarking |
P51898
|
FINISHED |
| Object | Slovak hiking trail network |
—
|
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: Slovak hiking trail network | Statement: [Veľký Rozsutec, touristMarking, Slovak hiking trail network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristMarking Context triple: [Veľký Rozsutec, touristMarking, Slovak hiking trail network]
-
A.
hasTouristSignage
chosen
Indicates that there is official signage present to guide or inform tourists about a place, route, or attraction.
-
B.
touristDesignation
Indicates that a place or entity has been formally identified or labeled as a tourist attraction or destination.
-
C.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
D.
hasMarkerOrMonument
Indicates that something possesses or is associated with a physical marker or monument commemorating it.
-
E.
hasGoalForTourists
Indicates that something is intended or designed to achieve a specific objective or benefit for tourists.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.