Triple
T31073408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udo Island |
E791883
|
entity |
| Predicate | nearbyAttractionOnJeju |
P7335
|
FINISHED |
| Object | Seongsan Ilchulbong (Sunrise Peak) |
—
|
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: Seongsan Ilchulbong (Sunrise Peak) | Statement: [Udo Island, nearbyAttractionOnJeju, Seongsan Ilchulbong (Sunrise Peak)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyAttractionOnJeju Context triple: [Udo Island, nearbyAttractionOnJeju, Seongsan Ilchulbong (Sunrise Peak)]
-
A.
touristAttractionIn
chosen
Indicates that a place functions as a tourist attraction located within a specified geographic area or entity.
-
B.
nearestTouristDestination
Indicates that one location is the closest tourist destination to another specified location.
-
C.
nearbyHeritageDestinations
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
-
D.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
E.
nearbyResortArea
Indicates that a resort area is located close to or within a short distance of a specified place or 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 9:01 p.m.