Triple

T24561331
Position Surface form Disambiguated ID Type / Status
Subject Battle of Plymouth (1652) E607661 entity
Predicate combatantCommander P1698 FINISHED
Object Cornelis de With
Cornelis de With was a 17th-century Dutch admiral of the United Provinces, noted for his prominent role in the First Anglo-Dutch War.
E1682740 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: Cornelis de With | Statement: [Battle of Plymouth (1652), combatantCommander, Cornelis de With]
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: Cornelis de With
Triple: [Battle of Plymouth (1652), combatantCommander, Cornelis de With]
Generated description
Cornelis de With was a 17th-century Dutch admiral of the United Provinces, noted for his prominent role in the First Anglo-Dutch War.

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_69e2c4cc35a48190990b7571bc086df8 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f63a348190a3c9fd96e3ad80b0 completed April 30, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a10ad244f1c819082d480ab8f4d05f4 completed May 22, 2026, 7:23 p.m.
NEDg Description generation batch_6a10ae2f577481909be995d38010dcf7 completed May 22, 2026, 7:27 p.m.
NED2 Entity disambiguation (via description) batch_6a10aef10de8819099e12e65f4f9e768 completed May 22, 2026, 7:30 p.m.
Created at: April 18, 2026, 2:28 a.m.