Triple

T35242853
Position Surface form Disambiguated ID Type / Status
Subject Lat Phrao Road E1017573 entity
Predicate connectsTo P845 FINISHED
Object Sukhonthasawat Road
Sukhonthasawat Road is a local thoroughfare in Bangkok, Thailand, serving residential and commercial areas and linking to major routes such as Lat Phrao Road.
E2187497 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: Sukhonthasawat Road | Statement: [Lat Phrao Road, connectsTo, Sukhonthasawat Road]
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: Sukhonthasawat Road
Triple: [Lat Phrao Road, connectsTo, Sukhonthasawat Road]
Generated description
Sukhonthasawat Road is a local thoroughfare in Bangkok, Thailand, serving residential and commercial areas and linking to major routes such as Lat Phrao Road.

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_69f76de235048190b990070c23c51b6b completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78f24b8048190ac4bea4af553256e completed May 3, 2026, 6:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39dbb0e9388190a5f7cef4ca7d8d3a completed June 23, 2026, 1:04 a.m.
NEDg Description generation batch_6a39dfec48e08190b42db43d49767409 completed June 23, 2026, 1:22 a.m.
NED2 Entity disambiguation (via description) batch_6a39e055f3988190a10d812e50672758 completed June 23, 2026, 1:24 a.m.
Created at: May 3, 2026, 4:02 p.m.