Triple

T26612142
Position Surface form Disambiguated ID Type / Status
Subject Masian Beach E667951 entity
Predicate hasAlternativeName P39 FINISHED
Object Masianhaebyeon
Masianhaebyeon is a popular coastal beach area in South Korea known for its expansive tidal flats, scenic sunsets, and proximity to Incheon International Airport.
E1731815 NE 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: Masianhaebyeon | Statement: [Masian Beach, hasAlternativeName, Masianhaebyeon]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Masianhaebyeon
Triple: [Masian Beach, hasAlternativeName, Masianhaebyeon]
Generated description
Masianhaebyeon is a popular coastal beach area in South Korea known for its expansive tidal flats, scenic sunsets, and proximity to Incheon International Airport.

Provenance (5 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_69ee9cfe16088190a3dddd68e3c7b1ea completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f615aa023c81908858893e8a7067af completed May 2, 2026, 3:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11c8479aa48190bde51181cb2a9fa1 completed May 23, 2026, 3:31 p.m.
NEDg Description generation batch_6a11c8f290bc8190bfa1990ee7119516 completed May 23, 2026, 3:34 p.m.
NED2 Entity disambiguation (via description) batch_6a11ca61b1408190ab4bda33e53cb27c completed May 23, 2026, 3:40 p.m.
Created at: April 27, 2026, 2:17 a.m.