Triple
T24792338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Миџор |
E620282
|
entity |
| Predicate | типТуризма |
P1769
|
FINISHED |
| Object | планински туризам |
—
|
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: планински туризам | Statement: [Миџор, типТуризма, планински туризам]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: типТуризма Context triple: [Миџор, типТуризма, планински туризам]
-
A.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
B.
countryTourismCategory
Indicates the tourism classification or category assigned to a country based on its tourism characteristics or status.
-
C.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
D.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
-
E.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110424188190889a13976b16b18a |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:47 a.m.