Triple

T31394301
Position Surface form Disambiguated ID Type / Status
Subject Achasan Mountain E800822 entity
Predicate near P350 FINISHED
Object Amsa-dong neighborhood of Seoul
Amsa-dong is a residential neighborhood in Seoul’s Gangdong District known for its riverside location along the Han River and nearby historic and natural sites.
E1962896 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: Amsa-dong neighborhood of Seoul | Statement: [Achasan Mountain, near, Amsa-dong neighborhood of Seoul]
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: Amsa-dong neighborhood of Seoul
Triple: [Achasan Mountain, near, Amsa-dong neighborhood of Seoul]
Generated description
Amsa-dong is a residential neighborhood in Seoul’s Gangdong District known for its riverside location along the Han River and nearby historic and natural sites.

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_69f224ea9998819086ae2e4f4f4091c8 completed April 29, 2026, 3:34 p.m.
NER Named-entity recognition batch_69f6a02ec5ec8190b172c1cb924e61f4 completed May 3, 2026, 1:09 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2b076ac71081909709d7b2a86b871a completed June 11, 2026, 7:07 p.m.
NEDg Description generation batch_6a2b0a3b1d488190879a6fc252c80ace completed June 11, 2026, 7:19 p.m.
NED2 Entity disambiguation (via description) batch_6a2b0a76a7388190b77fbeefb1b6b26e completed June 11, 2026, 7:20 p.m.
Created at: April 29, 2026, 9:19 p.m.