Triple
T13697597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galle Clock Tower |
E328427
|
entity |
| Predicate | significantForTourism |
P33214
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Galle Clock Tower, significantForTourism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantForTourism Context triple: [Galle Clock Tower, significantForTourism, yes]
-
A.
tourismImportance
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
B.
hasTourismPotential
Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
-
C.
tourismFeature
chosen
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
D.
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.
-
E.
hasTourismImpactOn
Indicates that one entity affects or influences the tourism levels, patterns, or attractiveness of another entity.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.