Triple
T24354234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ессентуки |
E613877
|
entity |
| Predicate | hasCulturalObject |
P155900
|
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: [Ессентуки, hasCulturalObject, курортный театр]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalObject Context triple: [Ессентуки, hasCulturalObject, курортный театр]
-
A.
hasCulturalProduct
Indicates that an entity possesses, produces, or is associated with a cultural artifact, work, or output (such as art, literature, music, or media).
-
B.
hasCulturalProperty
Indicates that something possesses or is associated with a cultural attribute, value, or characteristic.
-
C.
collectionIncludesCulture
Indicates that a collection contains, represents, or is associated with a particular culture.
-
D.
hasCulturalIcon
Indicates that an entity is associated with or possesses a person, symbol, or object widely recognized as a significant representation of a particular culture.
-
E.
hasCulturalHeritageOn
Indicates that one entity possesses, preserves, or is associated with the cultural heritage embodied in another entity.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29347e86881909cfbe5f23ce538b9 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 1:59 a.m.