Triple

T36563120
Position Surface form Disambiguated ID Type / Status
Subject Titiwangsa station E901895 entity
Predicate nearbyPlace P2064 FINISHED
Object Hospital Kuala Lumpur
Hospital Kuala Lumpur is one of Malaysia’s largest and oldest public hospitals, serving as a major tertiary referral and teaching hospital in the capital city.
E2188676 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: Hospital Kuala Lumpur | Statement: [Titiwangsa station, nearbyPlace, Hospital Kuala Lumpur]
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: Hospital Kuala Lumpur
Triple: [Titiwangsa station, nearbyPlace, Hospital Kuala Lumpur]
Generated description
Hospital Kuala Lumpur is one of Malaysia’s largest and oldest public hospitals, serving as a major tertiary referral and teaching hospital in the capital city.

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_69f76e634e9481908c9ba1b87ab87c26 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c27d4f5c8190ab080be352c846f3 completed May 3, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39e6f656f481908ba8357ffb65102e completed June 23, 2026, 1:52 a.m.
NEDg Description generation batch_6a39e7943be881909c7ed1ce33ad96d8 completed June 23, 2026, 1:55 a.m.
NED2 Entity disambiguation (via description) batch_6a39ea9c403c8190a44d9289b4fee998 completed June 23, 2026, 2:08 a.m.
Created at: May 3, 2026, 4:11 p.m.