Triple
T5095702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ischgl |
E114857
|
entity |
| Predicate | touristOrigin |
P21892
|
FINISHED |
| Object | international visitors |
—
|
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: international visitors | Statement: [Ischgl, touristOrigin, international visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristOrigin Context triple: [Ischgl, touristOrigin, international visitors]
-
A.
shareTourismFlows
Indicates that two places are connected by or exchange significant tourism flows, such as visitors or tourist traffic, between them.
-
B.
touristArrivalsShareInTerritory
Indicates the proportion of total tourist arrivals that occur within a specific territory relative to a larger reference area or total.
-
C.
touristArrivalsRank
Indicates the relative position of a place compared to others based on the number of tourists arriving there.
-
D.
touristArrivalsPerYearApprox
Indicates an approximate count of how many tourists arrive at a place over the course of a year.
-
E.
tourismFrom
chosen
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
- 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75652a8081908386718f1fdb1de3 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.