Triple

T6086063
Position Surface form Disambiguated ID Type / Status
Subject Philips van Almonde E135641 entity
Predicate familyName P18 FINISHED
Object van Almonde
Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
 E566438 NE FINISHED

How this triple was built (4 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: van Almonde | Statement: [Philips van Almonde, familyName, van Almonde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: van Almonde
Context triple: [Philips van Almonde, familyName, van Almonde]
  • A. van Egmond
    Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
  • B. van Amsberg
    Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
  • C. Van der Madeweg
    Van der Madeweg is a metro station in Amsterdam that serves as a stop on the city's rapid transit network.
  • D. van Dam
    van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
  • E. Winschoten
    Winschoten is a town in the northeast of the Netherlands known historically as a regional trade center and for its traditional windmills and Jewish heritage.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
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: van Almonde
Triple: [Philips van Almonde, familyName, van Almonde]
Generated description
Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: van Almonde
Target entity description: Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
  • A. van Egmond
    Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
  • B. van Amsberg
    Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
  • C. Van der Madeweg
    Van der Madeweg is a metro station in Amsterdam that serves as a stop on the city's rapid transit network.
  • D. van Dam
    van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
  • E. Winschoten
    Winschoten is a town in the northeast of the Netherlands known historically as a regional trade center and for its traditional windmills and Jewish heritage.
  • F. None of above. chosen

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_69c0087bcc788190b20f093d3a6c60ec completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0578a8b8081908490e447ae3419f9 completed March 22, 2026, 8:56 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11d60e824819098a9f5fc5cc00be4 completed March 23, 2026, 11 a.m.
NEDg Description generation batch_69c11e4454948190a8f4643cb55e673a completed March 23, 2026, 11:04 a.m.
NED2 Entity disambiguation (via description) batch_69c11ec554688190bfe184608944a15e completed March 23, 2026, 11:06 a.m.
Created at: March 22, 2026, 4:12 p.m.