Triple

T36295996
Position Surface form Disambiguated ID Type / Status
Subject Elchingen E893367 entity
Predicate hasTransportConnection P845 FINISHED
Object A8 motorway
The A8 motorway is a major German autobahn running east–west across southern Germany, connecting cities such as Karlsruhe, Stuttgart, Ulm, Augsburg, and Munich.
E1962473 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: A8 motorway | Statement: [Elchingen, hasTransportConnection, A8 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: A8 motorway
Triple: [Elchingen, hasTransportConnection, A8 motorway]
Generated description
The A8 motorway is a major German autobahn running east–west across southern Germany, connecting cities such as Karlsruhe, Stuttgart, Ulm, Augsburg, and Munich.

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_69f76e4a61f0819084a2b68dbbb4efc6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b9ff5fcc8190853d84e35db65aca completed May 3, 2026, 9:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a81c7bc02c48190950d447ad471d130 completed Aug. 16, 2026, 2:22 p.m.
NEDg Description generation batch_6a81c81fa08c8190a6869d802dfa5d1e completed Aug. 16, 2026, 2:24 p.m.
NED2 Entity disambiguation (via description) batch_6a81c86aaee481909d03256d5ce60b5a completed Aug. 16, 2026, 2:25 p.m.
Created at: May 3, 2026, 4:09 p.m.