Triple

T24104508
Position Surface form Disambiguated ID Type / Status
Subject Abu Dhabi–Dubai border E597183 entity
Predicate crossedBy P416 FINISHED
Object E611 highway
The E611 highway is a major United Arab Emirates roadway that serves as an outer bypass connecting key emirates and easing traffic between Abu Dhabi and Dubai.
E1620213 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: E611 highway | Statement: [Abu Dhabi–Dubai border, crossedBy, E611 highway]
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: E611 highway
Triple: [Abu Dhabi–Dubai border, crossedBy, E611 highway]
Generated description
The E611 highway is a major United Arab Emirates roadway that serves as an outer bypass connecting key emirates and easing traffic between Abu Dhabi and Dubai.

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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de1399108190986f604468cd5858 completed April 29, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fad14f8b08190969ce3eb65092366 completed May 22, 2026, 1:10 a.m.
NEDg Description generation batch_6a0fadf24a1c8190bf530988ba1b86de completed May 22, 2026, 1:14 a.m.
NED2 Entity disambiguation (via description) batch_6a0faeb55b6c8190944d1bd621b3f819 completed May 22, 2026, 1:17 a.m.
Created at: April 17, 2026, 11:01 p.m.