Triple
T26135087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudawy Janowickie |
E659355
|
entity |
| Predicate | hasTouristTrails |
P167071
|
FINISHED |
| Object | marked hiking trails |
—
|
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: marked hiking trails | Statement: [Rudawy Janowickie, hasTouristTrails, marked hiking trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristTrails Context triple: [Rudawy Janowickie, hasTouristTrails, marked hiking trails]
-
A.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
hasTrailheads
Indicates that one location or area contains or provides access points where trails begin.
-
C.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
D.
hasScenicRoutes
Indicates that one location, path, or area offers routes that are visually attractive or notable for their natural or aesthetic scenery.
-
E.
hasInterpretiveTrails
Indicates that an entity provides or features designated trails accompanied by informational or educational materials to help visitors interpret and understand the surroundings.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 8:17 p.m.