Triple
T8553413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trakt Królewski |
E202500
|
entity |
| Predicate | touristRouteType |
P19187
|
FINISHED |
| Object | urban cultural route |
—
|
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: urban cultural route | Statement: [Trakt Królewski, touristRouteType, urban cultural route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristRouteType Context triple: [Trakt Królewski, touristRouteType, urban cultural route]
-
A.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
C.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
D.
notableRouteType
chosen
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
E.
tourPattern
Indicates a recurring or structured sequence of visits or stops that defines how a tour is organized or carried out.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe8894e7c8190bc0ae2ceec473ecb |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.