Triple
T16334006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieter van Mierevelt |
E396628
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Pieter |
E57118
|
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: Pieter | Statement: [Pieter van Mierevelt, givenName, Pieter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pieter Context triple: [Pieter van Mierevelt, givenName, Pieter]
-
A.
Pieter
chosen
Pieter is the given first name of the influential Afrikaans poet, playwright, and essayist N. P. van Wyk Louw.
-
B.
Pieter Bout
Pieter Bout was a Flemish Baroque painter and draughtsman known for his lively landscapes, cityscapes, and genre scenes produced in the late 17th century.
-
C.
Pieter van Vliet
Pieter van Vliet is a Dutch-origin personal name associated with individuals bearing the surname Van Vliet.
-
D.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
E.
Piet
Piet is a masculine given name of Dutch origin, commonly used in the Netherlands and Belgium.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e1da1081909bec6e77e6109dce |
completed | April 17, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a004f3f93348190b835218ae42f3463 |
completed | May 10, 2026, 9:26 a.m. |
Created at: April 10, 2026, 5:07 a.m.