Triple

T36860932
Position Surface form Disambiguated ID Type / Status
Subject Asian Highway 32 E910932 entity
Predicate hasNetworkCode P57366 FINISHED
Object AH32
AH32 is a route in the Asian Highway Network that connects parts of Southeast Asia through an international road corridor.
E2203725 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: AH32 | Statement: [Asian Highway 32, hasNetworkCode, AH32]
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: AH32
Triple: [Asian Highway 32, hasNetworkCode, AH32]
Generated description
AH32 is a route in the Asian Highway Network that connects parts of Southeast Asia through an international road corridor.

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_69f76e80f6f0819091cba8e19b269615 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cfcfe7a881908820d8db6e519442 completed May 3, 2026, 10:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3dfadc6bc08190b9031f70b139246f completed June 26, 2026, 4:06 a.m.
NEDg Description generation batch_6a3dfd07722c8190bce1f21b79d1edb9 completed June 26, 2026, 4:16 a.m.
NED2 Entity disambiguation (via description) batch_6a3e0e15710c81908d8ea4fc007197d2 completed June 26, 2026, 5:28 a.m.
Created at: May 3, 2026, 4:13 p.m.