Triple

T23434309
Position Surface form Disambiguated ID Type / Status
Subject Mudan Township E563414 entity
Predicate hasTouristAttraction P530 FINISHED
Object Mudan Reservoir
Mudan Reservoir is a scenic man-made lake in Pingtung County, Taiwan, known for its surrounding mountain landscapes and role in local water supply and recreation.
E1607103 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: Mudan Reservoir | Statement: [Mudan Township, hasTouristAttraction, Mudan Reservoir]
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: Mudan Reservoir
Triple: [Mudan Township, hasTouristAttraction, Mudan Reservoir]
Generated description
Mudan Reservoir is a scenic man-made lake in Pingtung County, Taiwan, known for its surrounding mountain landscapes and role in local water supply and recreation.

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_69e24553980c8190bb66a2ae0bdab125 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a5daabcc819094446a80723a487b completed April 29, 2026, 6:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f75eb3ccc8190a792110c4ea432f9 completed May 21, 2026, 9:15 p.m.
NEDg Description generation batch_6a0f768c30b081908b64bd292b1749eb completed May 21, 2026, 9:18 p.m.
NED2 Entity disambiguation (via description) batch_6a0f77a3c6e4819080c8b07fc9dd5b62 completed May 21, 2026, 9:22 p.m.
Created at: April 17, 2026, 5:49 p.m.