Triple

T34029121
Position Surface form Disambiguated ID Type / Status
Subject Melk Abbey Chronicle E872593 entity
Predicate associatedPlace P1481 FINISHED
Object Melk, Austria
Melk, Austria is a small town on the Danube River best known for its magnificent Benedictine abbey, a masterpiece of Baroque architecture and a major cultural and historical landmark.
E2080007 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: Melk, Austria | Statement: [Melk Abbey Chronicle, associatedPlace, Melk, Austria]
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: Melk, Austria
Triple: [Melk Abbey Chronicle, associatedPlace, Melk, Austria]
Generated description
Melk, Austria is a small town on the Danube River best known for its magnificent Benedictine abbey, a masterpiece of Baroque architecture and a major cultural and historical landmark.

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_69f349a2527c81909a7cd4bda94d70ad completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f70b1cf9848190a1d68291da026de5 completed May 3, 2026, 8:45 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36ae4236cc81909b75384c9a3578d0 completed June 20, 2026, 3:14 p.m.
NEDg Description generation batch_6a36aebf5cd881909068286da30670c2 completed June 20, 2026, 3:16 p.m.
NED2 Entity disambiguation (via description) batch_6a36af3428dc8190aedbfd793f6ddf7c completed June 20, 2026, 3:18 p.m.
Created at: May 1, 2026, 1:51 a.m.