Triple
T23003401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koen |
E572693
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Coenraad |
E1566328
|
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: Coenraad | Statement: [Koen, hasVariant, Coenraad]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Coenraad Context triple: [Koen, hasVariant, Coenraad]
-
A.
Koenraad
chosen
Koenraad is a Dutch given name of Germanic origin, commonly associated with the meaning "bold advisor" or "brave counselor."
-
B.
Coenraad Jacob
Coenraad Jacob is the given name of Coenraad Jacob Temminck, a Dutch aristocrat and zoologist known for his foundational work in ornithology and mammalogy.
-
C.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
D.
Marnix
Marnix is a Dutch masculine given name commonly used in the Netherlands and Belgium.
-
E.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183549bdc81908fdcd44e2c92f7c4 |
completed | April 29, 2026, 4:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c159be4dc8190922c4c305e146aa9 |
completed | May 19, 2026, 7:47 a.m. |
Created at: April 17, 2026, 3:50 p.m.