Triple

T24559866
Position Surface form Disambiguated ID Type / Status
Subject Isselburg E607620 entity
Predicate hasTransportConnection P845 FINISHED
Object Bundesstraße 67
Bundesstraße 67 is a federal highway in western Germany that serves as an important regional route connecting several towns and cities in North Rhine-Westphalia.
E1695233 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: Bundesstraße 67 | Statement: [Isselburg, hasTransportConnection, Bundesstraße 67]
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: Bundesstraße 67
Triple: [Isselburg, hasTransportConnection, Bundesstraße 67]
Generated description
Bundesstraße 67 is a federal highway in western Germany that serves as an important regional route connecting several towns and cities in North Rhine-Westphalia.

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_69e2c4cc35a48190990b7571bc086df8 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f57a7c8190a0eb8d6d6ef6ae61 completed April 30, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10cba7276c8190b5ddf5b398e6e6ca completed May 22, 2026, 9:33 p.m.
NEDg Description generation batch_6a10cf6c1eb8819097ba0b8c949bc71a completed May 22, 2026, 9:49 p.m.
NED2 Entity disambiguation (via description) batch_6a10cfc8b81881908d2901a6f29a1506 completed May 22, 2026, 9:51 p.m.
Created at: April 18, 2026, 2:27 a.m.