Triple

T23426243
Position Surface form Disambiguated ID Type / Status
Subject Mostar interchange E560802 entity
Predicate connects P390 FINISHED
Object E-75 motorway
The E-75 motorway is a major north–south European route that runs from Norway through central and eastern Europe to Greece, serving as a key international transport corridor.
E2290450 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: E-75 motorway | Statement: [Mostar interchange, connects, E-75 motorway]
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: E-75 motorway
Triple: [Mostar interchange, connects, E-75 motorway]
Generated description
The E-75 motorway is a major north–south European route that runs from Norway through central and eastern Europe to Greece, serving as a key international transport 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_69e2454cb1108190ab21ada5411a7146 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f1a54a28a08190add6184a44c5005b completed April 29, 2026, 6:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5bcfb484188190bdca41e6e7437187 completed July 18, 2026, 7:10 p.m.
NEDg Description generation batch_6a5bd1c124c881908ecfcbe918348284 completed July 18, 2026, 7:19 p.m.
NED2 Entity disambiguation (via description) batch_6a5bd28552d88190a01c59518f3c3793 completed July 18, 2026, 7:22 p.m.
Created at: April 17, 2026, 5:47 p.m.