Triple

T31555817
Position Surface form Disambiguated ID Type / Status
Subject Innkreis Autobahn A8 – Meggenhofen junction E805123 entity
Predicate locatedNear P294 FINISHED
Object Meggenhofen
Meggenhofen is a municipality in Upper Austria known for its convenient location near the Innkreis Autobahn A8, providing easy regional and international road access.
E2012680 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: Meggenhofen | Statement: [Innkreis Autobahn A8 – Meggenhofen junction, locatedNear, Meggenhofen]
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: Meggenhofen
Triple: [Innkreis Autobahn A8 – Meggenhofen junction, locatedNear, Meggenhofen]
Generated description
Meggenhofen is a municipality in Upper Austria known for its convenient location near the Innkreis Autobahn A8, providing easy regional and international road access.

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_69f348d22e088190ad555d5bd42f9da0 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a7c4100c8190b7652b13eaadeee8 completed May 3, 2026, 1:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347b5f10f08190b7404e4c2fc62b10 completed June 18, 2026, 11:12 p.m.
NEDg Description generation batch_6a347cb4b3848190badc3f8bf4d184e8 completed June 18, 2026, 11:18 p.m.
NED2 Entity disambiguation (via description) batch_6a347da3535081908263b33d3a3045fa completed June 18, 2026, 11:22 p.m.
Created at: April 30, 2026, 10:13 p.m.