Triple
T1420376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Griboyedov Canal |
E30209
|
entity |
| Predicate | touristUse |
P1769
|
FINISHED |
| Object | sightseeing boat tours |
—
|
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: sightseeing boat tours | Statement: [Griboyedov Canal, touristUse, sightseeing boat tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristUse Context triple: [Griboyedov Canal, touristUse, sightseeing boat tours]
-
A.
touristAccess
Indicates that a place or resource is available for use or visitation by tourists.
-
B.
touristGatewayTo
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
C.
tourismFrom
Indicates that tourists or visitor activity originates from one place and is directed toward another location.
-
D.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
E.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40764ec8190b85de6befcb20dda |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.