Triple

T31340176
Position Surface form Disambiguated ID Type / Status
Subject Soldier of Orange E799284 entity
Predicate musicBy P1952 FINISHED
Object Rogier van Otterloo
Rogier van Otterloo was a Dutch composer and conductor best known for his influential film scores and work in popular and orchestral music in the Netherlands.
E1991539 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: Rogier van Otterloo | Statement: [Soldier of Orange, musicBy, Rogier van Otterloo]
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: Rogier van Otterloo
Triple: [Soldier of Orange, musicBy, Rogier van Otterloo]
Generated description
Rogier van Otterloo was a Dutch composer and conductor best known for his influential film scores and work in popular and orchestral music in the Netherlands.

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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69f1340a48190be75fd54fa524d3e completed May 3, 2026, 1:04 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2eddbfa460819094d10eb1de403bed completed June 14, 2026, 4:58 p.m.
NEDg Description generation batch_6a2edeb5dce08190b720e3eff918abc8 completed June 14, 2026, 5:02 p.m.
NED2 Entity disambiguation (via description) batch_6a2edf2f49048190869080a3d70f4434 completed June 14, 2026, 5:04 p.m.
Created at: April 29, 2026, 9:16 p.m.