Triple

T37922076
Position Surface form Disambiguated ID Type / Status
Subject Deutsches Referenzkorpus E945989 entity
Predicate abbreviation P43 FINISHED
Object DeReKo
DeReKo is a large, curated reference corpus of contemporary German language used for linguistic research and analysis.
E2248923 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: DeReKo | Statement: [Deutsches Referenzkorpus, abbreviation, DeReKo]
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: DeReKo
Triple: [Deutsches Referenzkorpus, abbreviation, DeReKo]
Generated description
DeReKo is a large, curated reference corpus of contemporary German language used for linguistic research and analysis.

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_69f76ef2ebd88190be5229f2621070b3 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbd7a91d081909c05cf142215e78a completed May 6, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410cd4bf748190be299c50e2a80c75 completed June 28, 2026, noon
NEDg Description generation batch_6a410d7165d481908f52e927359c1f62 completed June 28, 2026, 12:02 p.m.
NED2 Entity disambiguation (via description) batch_6a410e6fbc6c81908a367fef07563c72 completed June 28, 2026, 12:07 p.m.
Created at: May 3, 2026, 4:20 p.m.