Triple

T34905531
Position Surface form Disambiguated ID Type / Status
Subject Wien Neêrlands Bloed E1006715 entity
Predicate musicBy P1952 FINISHED
Object Johannes Bernardus van Bree
Johannes Bernardus van Bree was a 19th-century Dutch composer and conductor known for his contributions to Dutch national music and choral works.
E2155633 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: Johannes Bernardus van Bree | Statement: [Wien Neêrlands Bloed, musicBy, Johannes Bernardus van Bree]
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: Johannes Bernardus van Bree
Triple: [Wien Neêrlands Bloed, musicBy, Johannes Bernardus van Bree]
Generated description
Johannes Bernardus van Bree was a 19th-century Dutch composer and conductor known for his contributions to Dutch national music and choral works.

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_69f76dc1b4a081909b4c6e4d8ec0aa2d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f781ebfef08190a739f868df66d348 completed May 3, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3891467c5c819085ce9eeac0c54f4b completed June 22, 2026, 1:35 a.m.
NEDg Description generation batch_6a3891dc79dc8190bf2482158e0dabed completed June 22, 2026, 1:37 a.m.
NED2 Entity disambiguation (via description) batch_6a38925d7c688190afca1a703aea06c3 completed June 22, 2026, 1:39 a.m.
Created at: May 3, 2026, 4 p.m.