Triple

T27324568
Position Surface form Disambiguated ID Type / Status
Subject Ritterhude E689604 entity
Predicate railwayLine P848 FINISHED
Object Bremen–Bremerhaven railway
The Bremen–Bremerhaven railway is a key rail route in northern Germany that connects the city of Bremen with the port city of Bremerhaven, serving both passenger and freight traffic.
E1775941 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: Bremen–Bremerhaven railway | Statement: [Ritterhude, railwayLine, Bremen–Bremerhaven railway]
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: Bremen–Bremerhaven railway
Triple: [Ritterhude, railwayLine, Bremen–Bremerhaven railway]
Generated description
The Bremen–Bremerhaven railway is a key rail route in northern Germany that connects the city of Bremen with the port city of Bremerhaven, serving both passenger and freight traffic.

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_69ef355d4cb08190ab032c0a2e7d3753 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f627ed03ac8190a17ddacba96f8a48 completed May 2, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12bbc7a92081909f92d973743c8a24 completed May 24, 2026, 8:50 a.m.
NEDg Description generation batch_6a12bd4dacfc81908c61517b7286c35d completed May 24, 2026, 8:56 a.m.
NED2 Entity disambiguation (via description) batch_6a12bdeacda08190bfe8354ed2666d23 completed May 24, 2026, 8:59 a.m.
Created at: April 27, 2026, 11:35 a.m.