Triple
T27161177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varosha (abandoned quarter) |
E682663
|
entity |
| Predicate | notableVisitorsBefore1974 |
P146835
|
FINISHED |
| Object | international tourists |
—
|
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 tourists | Statement: [Varosha (abandoned quarter), notableVisitorsBefore1974, international tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVisitorsBefore1974 Context triple: [Varosha (abandoned quarter), notableVisitorsBefore1974, international tourists]
-
A.
notableVisit
Indicates that one entity made a visit to another entity or location that is considered significant or noteworthy.
-
B.
notableIndividuals
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
C.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
D.
hasNotableResidentInTimeline
Indicates that an entity has, at some point in its historical timeline, a notable resident associated with it.
-
E.
reputedToBeVisitedBy
chosen
Indicates that an entity is commonly believed or reported to be visited by another entity, without necessarily confirming that the visits actually occur.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: April 27, 2026, 9:18 a.m.