Triple

T18965199
Position Surface form Disambiguated ID Type / Status
Subject Autobahn A46 E464015 entity
Predicate startPoint P389 FINISHED
Object Heinsberg NE NERFINISHED

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: Heinsberg | Statement: [Autobahn A46, startPoint, Heinsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heinsberg
Context triple: [Autobahn A46, startPoint, Heinsberg]
  • A. Heinsberg chosen
    Heinsberg is a town in western Germany’s North Rhine-Westphalia near the Dutch border, known as the administrative center of the Heinsberg district.
  • B. Neunkirchen
    Neunkirchen is an industrial town in Austria’s Lower Austria region, known historically for its manufacturing and metalworking industries.
  • C. Neunkirchen
    Neunkirchen is a town in southwestern Germany known as one of the major urban centers and former industrial hubs of the state of Saarland.
  • D. Andernach
    Andernach is a historic German town on the Rhine River in Rhineland-Palatinate, known for its medieval architecture and one of the world’s highest cold-water geysers.
  • E. Bitburg
    Bitburg is a town in western Germany’s Eifel region, best known internationally for its Bitburger brewery and its nearby World War II military cemetery.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8dcffc278819086792a4ebfddfafa completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d5d663948190b496fbd2e69c7f43 completed April 20, 2026, 7:29 a.m.
Created at: April 10, 2026, noon