Triple

T27975302
Position Surface form Disambiguated ID Type / Status
Subject Tehran urban road network E706470 entity
Predicate hasMajorComponent P15759 FINISHED
Object Sadr Expressway
Sadr Expressway is a major elevated highway in northern Tehran that serves as a key east–west traffic corridor in the city’s road network.
E1809414 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: Sadr Expressway | Statement: [Tehran urban road network, hasMajorComponent, Sadr Expressway]
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: Sadr Expressway
Triple: [Tehran urban road network, hasMajorComponent, Sadr Expressway]
Generated description
Sadr Expressway is a major elevated highway in northern Tehran that serves as a key east–west traffic corridor in the city’s road network.

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_69ef96b7f330819090f315318ba6977e completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63b38a5c081908edb1c9a415c914b completed May 2, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15e68fea748190bd66d5ec3e381719 completed May 26, 2026, 6:29 p.m.
NEDg Description generation batch_6a15e81c9a008190967efeb8537d30a6 completed May 26, 2026, 6:36 p.m.
NED2 Entity disambiguation (via description) batch_6a15fd3cc1448190a309a11d245a07b9 completed May 26, 2026, 8:06 p.m.
Created at: April 27, 2026, 7:40 p.m.