Triple
T21343868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woody Island |
E526274
|
entity |
| Predicate | hasTourismFacilities |
P7835
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Woody Island, hasTourismFacilities, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismFacilities Context triple: [Woody Island, hasTourismFacilities, limited]
-
A.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
B.
hasTouristInfrastructure
chosen
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
C.
hasTourismResource
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
D.
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.
-
E.
hasTourismPotential
Indicates that a place or resource possesses qualities that make it attractive or suitable for tourism activities or development.
- 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_69e0b51c33048190ab27cede74ef798c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8a85274f481909e699b390bed9350 |
completed | April 22, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:44 p.m.