Triple
T8304397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place Franz Liszt |
E194425
|
entity |
| Predicate | tourismAttractiveness |
P7889
|
FINISHED |
| Object | popular with visitors |
—
|
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: popular with visitors | Statement: [Place Franz Liszt, tourismAttractiveness, popular with visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismAttractiveness Context triple: [Place Franz Liszt, tourismAttractiveness, popular with visitors]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismDraw
Indicates that one entity attracts tourists or visitor interest to another entity or location.
-
C.
hasTourismRating
Indicates that an entity has been assigned a specific tourism-related quality or rating, reflecting its appeal or suitability for tourists.
-
D.
tourismImportance
chosen
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
E.
tourismTheme
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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8b9f6081909100d1da8a078616 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.