Triple
T6780075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendrik Merkus de Kock |
E155656
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hendrik |
E104689
|
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: Hendrik | Statement: [Hendrik Merkus de Kock, givenName, Hendrik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hendrik Context triple: [Hendrik Merkus de Kock, givenName, Hendrik]
-
A.
Hendrik
chosen
Hendrik is a masculine given name of Germanic origin, commonly used in Dutch- and German-speaking countries and related to the name Henry.
-
B.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
C.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
D.
Dirck
Dirck is a Dutch masculine given name historically borne by several notable figures, including artists of the Dutch Golden Age.
-
E.
Jan Hendrik
Jan Hendrik is the given first name of the renowned Dutch astronomer Jan Oort, a pioneer in the study of the Milky Way and the hypothesized Oort Cloud.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d26b32c0819093f86b1002260660 |
completed | March 27, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c71a8263508190ad5cace74d7d7ac2 |
completed | March 28, 2026, 12:02 a.m. |
Created at: March 27, 2026, 2:14 p.m.