Triple
T8398000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitiawan |
E198100
|
entity |
| Predicate | hasNearbyTouristGateway |
P17407
|
FINISHED |
| Object | gateway to Pangkor Island via Lumut |
—
|
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 Pangkor Island via Lumut | Statement: [Sitiawan, hasNearbyTouristGateway, gateway to Pangkor Island via Lumut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTouristGateway Context triple: [Sitiawan, hasNearbyTouristGateway, gateway to Pangkor Island via Lumut]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
D.
touristGatewayTo
chosen
Indicates a relationship where one place serves as the primary access point or entry hub for tourists visiting another place.
-
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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb818a8dc081908efd5d7f910322e7 |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:04 p.m.