Triple
T26667967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palacio de Sada |
E672238
|
entity |
| Predicate | hasTourismInformationCenter |
P171407
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Palacio de Sada, hasTourismInformationCenter, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismInformationCenter Context triple: [Palacio de Sada, hasTourismInformationCenter, yes]
-
A.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
B.
hasTourismHub
Indicates that a place functions as a central location or focal point for tourism-related activities, services, or attractions for another place or region.
-
C.
hasVisitorCenterBy
Indicates that a location or site is served or administered by a specific visitor center.
-
D.
hasTourismOrganization
Indicates that a place or destination is associated with a specific organization responsible for managing, promoting, or coordinating its tourism activities.
-
E.
hasInformationCenterFor
Indicates that one entity serves as an information center dedicated to providing information or services related to another entity.
- F. None of above. chosen
Provenance (4 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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69edae2448190925ce701c8792c52 |
completed | May 3, 2026, 1:03 a.m. |
Created at: April 27, 2026, 3:11 a.m.