Triple
T19378497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrnambool region |
E484732
|
entity |
| Predicate | touristRouteRole |
P36629
|
FINISHED |
| Object | gateway to the Shipwreck Coast |
—
|
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: gateway to the Shipwreck Coast | Statement: [Warrnambool region, touristRouteRole, gateway to the Shipwreck Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristRouteRole Context triple: [Warrnambool region, touristRouteRole, gateway to the Shipwreck Coast]
-
A.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
B.
isMajorTourismRoute
Indicates that a route serves as a primary corridor for significant tourism-related travel and activities.
-
C.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
D.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
E.
routeRole
chosen
Indicates the specific functional role or purpose that an entity has within a particular route or path.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5dc3048190830b55c8ca02e624 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.