Triple

T24673448
Position Surface form Disambiguated ID Type / Status
Subject Haeundae District, Busan E610908 entity
Predicate hasLandmark P105 FINISHED
Object Jangsan Mountain
Jangsan Mountain is a prominent peak in Busan known for its hiking trails, scenic city and sea views, and natural landscapes overlooking the Haeundae area.
E1651973 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: Jangsan Mountain | Statement: [Haeundae District, Busan, hasLandmark, Jangsan Mountain]
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: Jangsan Mountain
Triple: [Haeundae District, Busan, hasLandmark, Jangsan Mountain]
Generated description
Jangsan Mountain is a prominent peak in Busan known for its hiking trails, scenic city and sea views, and natural landscapes overlooking the Haeundae area.

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_69e2c4d505cc8190981881df06c0bf52 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f40fae13c88190a41951febdf1791f completed May 1, 2026, 2:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a101bedbe6481908d0d4cb4276806e4 completed May 22, 2026, 9:03 a.m.
NEDg Description generation batch_6a1025d98060819088e468adf0b027f2 completed May 22, 2026, 9:46 a.m.
NED2 Entity disambiguation (via description) batch_6a1026ce819481909ef52667084ebced completed May 22, 2026, 9:50 a.m.
Created at: April 18, 2026, 2:50 a.m.