Triple
T18424132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vis |
E442093
|
entity |
| Predicate | wasClosedToForeignTouristsUntil |
P113019
|
FINISHED |
| Object | 1989 |
—
|
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: 1989 | Statement: [Vis, wasClosedToForeignTouristsUntil, 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasClosedToForeignTouristsUntil Context triple: [Vis, wasClosedToForeignTouristsUntil, 1989]
-
A.
wasRestrictedToForeigners
Indicates that access, use, or participation was limited exclusively to foreigners rather than locals.
-
B.
hasTourismRestriction
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
-
C.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
D.
notOpenToGeneralPublic
Indicates that access to the subject is restricted and not available to the general public.
-
E.
wasClosedCity
chosen
Indicates that a city was officially designated as a "closed city," restricting access, residency, or movement due to security, military, or political reasons.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51b102dd88190af474902fe58ead5 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.