Triple
T30432330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Нарышкин бастион |
E774203
|
entity |
| Predicate | туристическаяРоль |
P33155
|
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.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
B.
travelRouteRole
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
-
C.
tourRole
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
D.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
E.
hasTourismFunction
chosen
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866fb024819091c91f76b990a381 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:07 p.m.