Triple
T23675652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Сорочинці |
E584864
|
entity |
| Predicate | туристичнаПривабливість |
P27612
|
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.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
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.
-
C.
tourismMotivation
Indicates the reasons or driving factors that motivate an entity (typically a person) to engage in tourism or travel activities.
-
D.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
E.
tourismTheme
chosen
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f2e35c8190ada29694e2cbed37 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.