Triple

T23216853
Position Surface form Disambiguated ID Type / Status
Subject Eunpyeong-gu E580767 entity
Predicate hasNeighborhood P40 FINISHED
Object Nokbeon-dong
Nokbeon-dong is a residential neighborhood in the Eunpyeong District of northwestern Seoul, South Korea, known for its local markets, schools, and convenient access to central Seoul.
E1817295 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: Nokbeon-dong | Statement: [Eunpyeong-gu, hasNeighborhood, Nokbeon-dong]
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: Nokbeon-dong
Triple: [Eunpyeong-gu, hasNeighborhood, Nokbeon-dong]
Generated description
Nokbeon-dong is a residential neighborhood in the Eunpyeong District of northwestern Seoul, South Korea, known for its local markets, schools, and convenient access to central Seoul.

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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f19165949c81908e4d66a8a2b0a25a completed April 29, 2026, 5:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1632d0f8f081908eea6ced1f8dc412 completed May 26, 2026, 11:54 p.m.
NEDg Description generation batch_6a1633f6ab3c819084c6626f012a75da completed May 26, 2026, 11:59 p.m.
NED2 Entity disambiguation (via description) batch_6a16350e130c8190a9a73ee1edce0928 completed May 27, 2026, 12:04 a.m.
Created at: April 17, 2026, 4:08 p.m.