Triple
T26952527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cueva del Viento |
E678811
|
entity |
| Predicate | hasTouristCenterIn |
P59027
|
FINISHED |
| Object | Icod de los Vinos |
—
|
NE NERFINISHED |
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: Icod de los Vinos | Statement: [Cueva del Viento, hasTouristCenterIn, Icod de los Vinos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristCenterIn Context triple: [Cueva del Viento, hasTouristCenterIn, Icod de los Vinos]
-
A.
hasTourismInformationCenter
Indicates that a place or area contains or is served by a tourism information center providing guidance and services to visitors.
-
B.
hasVisitorCenterIn
chosen
Indicates that an entity operates or possesses a visitor center located within a specified place.
-
C.
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).
-
D.
hasVisitorCenterBy
Indicates that a location or site is served or administered by a specific visitor center.
-
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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 6:25 a.m.