Triple
T29295635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malé Atoll |
E742818
|
entity |
| Predicate | hasTouristResorts |
P55845
|
FINISHED |
| Object | multiple island resorts |
—
|
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: multiple island resorts | Statement: [Malé Atoll, hasTouristResorts, multiple island resorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouristResorts Context triple: [Malé Atoll, hasTouristResorts, multiple island resorts]
-
A.
hasTourismResource
chosen
Indicates that a place, area, or entity possesses or is associated with a tourism-related resource, attraction, or facility.
-
B.
hasTouristInfrastructure
Indicates that a place is equipped with facilities and services designed to support and accommodate tourists.
-
C.
hasTourismFunction
Indicates that an entity serves a role or purpose related to tourism, such as attracting, accommodating, or providing services to tourists.
-
D.
areMajorTouristDestinations
Indicates that the referenced places are widely recognized and frequently visited as primary tourist destinations.
-
E.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 1:06 p.m.