Triple

T37300779
Position Surface form Disambiguated ID Type / Status
Subject Taman Melawati E925933 entity
Predicate roadAccessVia P9041 FINISHED
Object Jalan Ulu Klang
Jalan Ulu Klang is a major roadway in the Klang Valley region of Selangor, Malaysia, serving as an important connector between various suburban townships and Kuala Lumpur.
E2223952 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: Jalan Ulu Klang | Statement: [Taman Melawati, roadAccessVia, Jalan Ulu Klang]
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: Jalan Ulu Klang
Triple: [Taman Melawati, roadAccessVia, Jalan Ulu Klang]
Generated description
Jalan Ulu Klang is a major roadway in the Klang Valley region of Selangor, Malaysia, serving as an important connector between various suburban townships and Kuala Lumpur.

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_69f76eb1bc508190924e9fa5d8acdeb3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fb5af0cb948190ab75de505cfb4d77 completed May 6, 2026, 3:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a406ccf1e5881908880036807ef4d40 completed June 28, 2026, 12:37 a.m.
NEDg Description generation batch_6a406e242e7081908e113c388eb1e6e1 completed June 28, 2026, 12:43 a.m.
NED2 Entity disambiguation (via description) batch_6a406eb8d9ac8190a8bd1aaeb4a5c9b1 completed June 28, 2026, 12:45 a.m.
Created at: May 3, 2026, 4:16 p.m.