Triple

T31994890
Position Surface form Disambiguated ID Type / Status
Subject Yangshuo County E816967 entity
Predicate hasScenicArea P29946 FINISHED
Object Xingping Town
Xingping Town is a historic riverside town in Guangxi, China, famed for its dramatic karst mountain scenery along the Li River and well-preserved traditional architecture.
E1990400 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: Xingping Town | Statement: [Yangshuo County, hasScenicArea, Xingping Town]
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: Xingping Town
Triple: [Yangshuo County, hasScenicArea, Xingping Town]
Generated description
Xingping Town is a historic riverside town in Guangxi, China, famed for its dramatic karst mountain scenery along the Li River and well-preserved traditional architecture.

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_69f348f8002081909a3588758ba94afb completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b3f782788190aa4b2dfa9e6eab19 completed May 3, 2026, 2:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2eddd342148190ab6a00773827fdc3 completed June 14, 2026, 4:58 p.m.
NEDg Description generation batch_6a2ede66f14c8190886168756794a63e completed June 14, 2026, 5:01 p.m.
NED2 Entity disambiguation (via description) batch_6a2edfcbf05481908b10310ec4536277 completed June 14, 2026, 5:07 p.m.
Created at: May 1, 2026, 12:13 a.m.