Triple
T12810497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolution Square |
E306256
|
entity |
| Predicate | isTouristStopOn |
P56381
|
FINISHED |
| Object | Havana city 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: Havana city tours | Statement: [Revolution Square, isTouristStopOn, Havana city tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTouristStopOn Context triple: [Revolution Square, isTouristStopOn, Havana city tours]
-
A.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
B.
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).
-
C.
tourStopOf
chosen
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
-
D.
isPartOfTouristArea
Indicates that one entity is located within or belongs to a designated tourist area or tourist-focused region.
-
E.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e817598819080fdd61e9d61236e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.