Triple
T4570238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yadnya Kasada |
E123011
|
entity |
| Predicate | tourismAspect |
P33214
|
FINISHED |
| Object | attracts domestic tourists |
—
|
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: attracts domestic tourists | Statement: [Yadnya Kasada, tourismAspect, attracts domestic tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourismAspect Context triple: [Yadnya Kasada, tourismAspect, attracts domestic tourists]
-
A.
tourismFeature
chosen
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
tourismTheme
Indicates the main subject or focus of a tourism-related activity, service, or destination (such as cultural, adventure, or eco-tourism).
-
C.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
D.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
E.
tourismImportance
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c3eba48190af1fce6e1ca16943 |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.