Triple
T13453985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jal Mahal |
E311179
|
entity |
| Predicate | cityTourismImportance |
P7889
|
FINISHED |
| Object | major landmark of Jaipur |
—
|
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: major landmark of Jaipur | Statement: [Jal Mahal, cityTourismImportance, major landmark of Jaipur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityTourismImportance Context triple: [Jal Mahal, cityTourismImportance, major landmark of Jaipur]
-
A.
tourismImportance
chosen
Indicates the degree to which a place or entity is significant or valuable as a destination or attraction for tourists.
-
B.
primaryTourismHub
Indicates that a location serves as the main center or focal point for tourism activities within a given area or region.
-
C.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
D.
hasTourismImpactOn
Indicates that one entity affects or influences the tourism levels, patterns, or attractiveness of another entity.
-
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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaefc52448190b30d7999f44a9765 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.