Triple

T35760622
Position Surface form Disambiguated ID Type / Status
Subject Het Trippenhuis E1033558 entity
Predicate builtFor P1261 FINISHED
Object Hendrick Trip
Hendrick Trip was a wealthy 17th-century Dutch arms dealer and merchant whose fortune and status are reflected in the grand Amsterdam canal mansion known as the Trippenhuis.
E2153928 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: Hendrick Trip | Statement: [Het Trippenhuis, builtFor, Hendrick Trip]
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: Hendrick Trip
Triple: [Het Trippenhuis, builtFor, Hendrick Trip]
Generated description
Hendrick Trip was a wealthy 17th-century Dutch arms dealer and merchant whose fortune and status are reflected in the grand Amsterdam canal mansion known as the Trippenhuis.

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_69f76e1262f48190a313318665acc189 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a1c496808190a84be6315eb4c9fa completed May 3, 2026, 7:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3885fa49b081909e4a9227938bc7ee completed June 22, 2026, 12:46 a.m.
NEDg Description generation batch_6a38866a9e948190a5aa2f80ee5921c0 completed June 22, 2026, 12:48 a.m.
NED2 Entity disambiguation (via description) batch_6a3886e8a5fc8190b77589a42dd8bb96 completed June 22, 2026, 12:50 a.m.
Created at: May 3, 2026, 4:06 p.m.