Triple
T35652278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rantepao |
E1030184
|
entity |
| Predicate | isTourismCenterOf |
P158315
|
FINISHED |
| Object | Tana Toraja region |
—
|
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: Tana Toraja region | Statement: [Rantepao, isTourismCenterOf, Tana Toraja region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTourismCenterOf Context triple: [Rantepao, isTourismCenterOf, Tana Toraja region]
-
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.
hasTouristAttractionRole
Indicates that an entity serves in the capacity or function of a tourist attraction for another entity (such as a place, organization, or area).
-
E.
isTourismSiteIn
Indicates that a tourism site is located within or belongs to a specified geographic or administrative area.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f751e9c81909b8d9b6a7d6604be |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.