Triple

T35398819
Position Surface form Disambiguated ID Type / Status
Subject Bang Sue district E1023161 entity
Predicate hasRoad P959 FINISHED
Object Pracharat Sai 7 Road
Pracharat Sai 7 Road is a local thoroughfare located in Bangkok’s Bang Sue district, serving residential and commercial areas in this part of the city.
E2210052 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: Pracharat Sai 7 Road | Statement: [Bang Sue district, hasRoad, Pracharat Sai 7 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: Pracharat Sai 7 Road
Triple: [Bang Sue district, hasRoad, Pracharat Sai 7 Road]
Generated description
Pracharat Sai 7 Road is a local thoroughfare located in Bangkok’s Bang Sue district, serving residential and commercial areas in this part of the 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_69f76df43ca4819098711ca4370f1bb9 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f795392adc8190becbe6ab9fd432ca completed May 3, 2026, 6:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3e8c1390c4819084f740a29c6a156c completed June 26, 2026, 2:26 p.m.
NEDg Description generation batch_6a3e94bce86c8190b025e79699e31e7e completed June 26, 2026, 3:03 p.m.
NED2 Entity disambiguation (via description) batch_6a3e9e99bdf081909934fab6490220d7 completed June 26, 2026, 3:45 p.m.
Created at: May 3, 2026, 4:03 p.m.