Triple
T26536568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anamalai Tiger Reserve |
E671265
|
entity |
| Predicate | hasTourismZone |
P52326
|
FINISHED |
| Object | Topslip |
—
|
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: Topslip | Statement: [Anamalai Tiger Reserve, hasTourismZone, Topslip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismZone Context triple: [Anamalai Tiger Reserve, hasTourismZone, Topslip]
-
A.
containsTouristArea
chosen
Indicates that a place or region includes within its boundaries an area primarily designated or recognized for tourism activities.
-
B.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
C.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
D.
hasTourismHub
Indicates that a place functions as a central location or focal point for tourism-related activities, services, or attractions for another place or region.
-
E.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 1:39 a.m.