Triple
T23708327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ternopil Lake |
E585791
|
entity |
| Predicate | isTourismSymbolOf |
P68764
|
FINISHED |
| Object | Ternopil |
—
|
NE NERFINISHED |
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: Ternopil | Statement: [Ternopil Lake, isTourismSymbolOf, Ternopil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTourismSymbolOf Context triple: [Ternopil Lake, isTourismSymbolOf, Ternopil]
-
A.
areMajorTouristDestinations
Indicates that the referenced places are widely recognized and frequently visited as primary tourist destinations.
-
B.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
C.
alsoAttractsTouristsIn
Indicates that a place, in addition to another, draws or appeals to tourists within a specified location or context.
-
D.
hasTouristAttractionRole
chosen
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
majorTouristDestinationSince
Indicates that a place has been widely recognized and frequented as a major tourist destination starting from a specified point in time.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b68868ac8190824cdd7eb9fb2f06 |
completed | April 29, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.