Triple

T25747890
Position Surface form Disambiguated ID Type / Status
Subject Jung District, Incheon E648391 entity
Predicate contains P35 FINISHED
Object Eulwang-ri Beach
Eulwang-ri Beach is a popular seaside destination near Incheon, South Korea, known for its wide sandy shore, scenic sunsets, and proximity to Incheon International Airport.
E1693397 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: Eulwang-ri Beach | Statement: [Jung District, Incheon, contains, Eulwang-ri Beach]
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: Eulwang-ri Beach
Triple: [Jung District, Incheon, contains, Eulwang-ri Beach]
Generated description
Eulwang-ri Beach is a popular seaside destination near Incheon, South Korea, known for its wide sandy shore, 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_69e7ab306eec8190b05c312c6ab186b8 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f5fd2075f48190926b27fd068fb371 completed May 2, 2026, 1:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10cc0bae188190a7cff24822f6cb46 completed May 22, 2026, 9:35 p.m.
NEDg Description generation batch_6a10ce130c1c8190b489dab50c45458a completed May 22, 2026, 9:43 p.m.
NED2 Entity disambiguation (via description) batch_6a10ce436c388190bd5093247022e624 completed May 22, 2026, 9:44 p.m.
Created at: April 22, 2026, 3:53 a.m.