Triple
T24990976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rakcham |
E625446
|
entity |
| Predicate | isPartOfTouristCircuit |
P32586
|
FINISHED |
| Object | Kinnaur tourism circuit |
—
|
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: Kinnaur tourism circuit | Statement: [Rakcham, isPartOfTouristCircuit, Kinnaur tourism circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfTouristCircuit Context triple: [Rakcham, isPartOfTouristCircuit, Kinnaur tourism circuit]
-
A.
isPartOfTouristArea
chosen
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
B.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
C.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
isMajorTourismRoute
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
E.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
- 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 18, 2026, 6:03 a.m.