Triple

T30514161

Position	Surface form	Disambiguated ID	Type / Status
Subject	Prague–Plzeň	`E776511`	entity
Predicate	partOf	`P40`	FINISHED
Object	Prague–Munich corridor The Prague–Munich corridor is a major trans-European transport route linking the Czech capital Prague with Munich in Germany, facilitating significant regional and international rail and road connectivity.	`E1922069`	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: Prague–Munich corridor | Statement: [Prague–Plzeň, partOf, Prague–Munich corridor]

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: Prague–Munich corridor
Triple: [Prague–Plzeň, partOf, Prague–Munich corridor]

Generated description

The Prague–Munich corridor is a major trans-European transport route linking the Czech capital Prague with Munich in Germany, facilitating significant regional and international rail and road connectivity.

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_69f2249b23c4819087fa85496d92f43f`	completed	April 29, 2026, 3:32 p.m.
NER	Named-entity recognition	`batch_69f687bbdd288190bb65643dd7a12b07`	completed	May 2, 2026, 11:24 p.m.
NED1	Entity disambiguation (via context triple)	`batch_6a2856eb4d5881909521294dc6f47330`	completed	June 9, 2026, 6:09 p.m.
NEDg	Description generation	`batch_6a28594a96708190be0c4f1c4b18fccb`	completed	June 9, 2026, 6:19 p.m.
NED2	Entity disambiguation (via description)	`batch_6a285d23431881908ba2c38328d4cfb8`	completed	June 9, 2026, 6:36 p.m.

Created at: April 29, 2026, 8:16 p.m.