Triple
T16039501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harman Gerritszoon van Rijn |
E389056
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Rijn |
E1099001
|
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: van Rijn | Statement: [Harman Gerritszoon van Rijn, familyName, van Rijn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Rijn Context triple: [Harman Gerritszoon van Rijn, familyName, van Rijn]
-
A.
van Rijn
chosen
van Rijn is a Dutch surname most famously associated with the painter Rembrandt van Rijn.
-
B.
van Mieris
Van Mieris is the surname of a notable Dutch family of painters active during the 17th and 18th centuries, including Frans van Mieris the Elder.
-
C.
Vermeer
Vermeer is a brand of industrial and agricultural equipment known for machinery such as trenchers, wood chippers, and balers.
-
D.
Harman Gerritszoon van Rijn
Harman Gerritszoon van Rijn was a Dutch miller and the paternal grandfather of the painter Rembrandt van Rijn.
-
E.
Geertruy Vermeer
Geertruy Vermeer was a member of the Vermeer family, likely related to the Dutch painter Johannes Vermeer and part of his immediate familial circle in 17th-century Delft.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833f84188190baa3a452df880284 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbd77c5481908644742a8a8f3e68 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 4:56 a.m.