Triple

T38638402
Position Surface form Disambiguated ID Type / Status
Subject Krems River (Upper Austria) E938521 entity
Predicate partOf P40 FINISHED
Object Traun River basin
The Traun River basin is a major river catchment area in Upper Austria that drains numerous tributaries, including the Krems River, into the Traun River system.
E2282006 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: Traun River basin | Statement: [Krems River (Upper Austria), partOf, Traun River basin]
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: Traun River basin
Triple: [Krems River (Upper Austria), partOf, Traun River basin]
Generated description
The Traun River basin is a major river catchment area in Upper Austria that drains numerous tributaries, including the Krems River, into the Traun River system.

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_69f76ed948ec81908ce7811608a8f359 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd9b8e3c88190a3a56e103483aba0 completed May 7, 2026, 6:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a420dffe7148190bdcbc7c8144e8c04 completed June 29, 2026, 6:17 a.m.
NEDg Description generation batch_6a420e962d948190ae48e6e87e19a82a completed June 29, 2026, 6:20 a.m.
NED2 Entity disambiguation (via description) batch_6a420f4106fc819089d72df446df93a2 completed June 29, 2026, 6:22 a.m.
Created at: May 3, 2026, 4:32 p.m.