Triple
T24992333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitsunday Regional Council |
E625478
|
entity |
| Predicate | hasPopularTouristDestination |
P158315
|
FINISHED |
| Object | Airlie Beach |
—
|
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: Airlie Beach | Statement: [Whitsunday Regional Council, hasPopularTouristDestination, Airlie Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularTouristDestination Context triple: [Whitsunday Regional Council, hasPopularTouristDestination, Airlie Beach]
-
A.
isTouristDestination
Indicates that a place is recognized as a location people commonly visit for leisure, sightseeing, or travel.
-
B.
isPopularTouristDestinationIn
chosen
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
-
C.
areMajorTouristDestinations
Indicates that the referenced places are widely recognized and frequently visited as primary tourist destinations.
-
D.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:04 a.m.