Triple
T22747861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Fabian |
E562602
|
entity |
| Predicate | hasTourismAsset |
P55845
|
FINISHED |
| Object | public beaches |
—
|
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: public beaches | Statement: [San Fabian, hasTourismAsset, public beaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismAsset Context triple: [San Fabian, hasTourismAsset, public beaches]
-
A.
hasTourismResource
chosen
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
B.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
C.
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.
-
D.
hasTourismOrganization
Indicates that a place or destination is associated with a specific organization responsible for managing, promoting, or coordinating its tourism activities.
-
E.
hasTourismStyle
Indicates the type or style of tourism associated with or characteristic of a particular entity.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b702388190b134dde5f80ea3cd |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:24 p.m.