Triple

T26667425
Position Surface form Disambiguated ID Type / Status
Subject German A30 motorway E672224 entity
Predicate hasJunctionWith P1018 FINISHED
Object Bundesautobahn 31
Bundesautobahn 31 is a major north–south German motorway running from the North Sea coast near Emden down through western Germany toward the Ruhr area.
E1845341 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: Bundesautobahn 31 | Statement: [German A30 motorway, hasJunctionWith, Bundesautobahn 31]
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: Bundesautobahn 31
Triple: [German A30 motorway, hasJunctionWith, Bundesautobahn 31]
Generated description
Bundesautobahn 31 is a major north–south German motorway running from the North Sea coast near Emden down through western Germany toward the Ruhr area.

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_69eecda00a9c8190b2691f4d89db03b6 completed April 27, 2026, 2:44 a.m.
NER Named-entity recognition batch_69f616c4dda8819088c175f27c5f0961 completed May 2, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25057cbba48190bd1546ffede844f9 completed June 7, 2026, 5:45 a.m.
NEDg Description generation batch_6a2509a2a3b08190b3fde8083c80eef6 completed June 7, 2026, 6:03 a.m.
NED2 Entity disambiguation (via description) batch_6a250e036044819085e601b07f88a7ff completed June 7, 2026, 6:21 a.m.
Created at: April 27, 2026, 3:10 a.m.