Triple
T5002404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maartenszen |
E112403
|
entity |
| Predicate | isRelatedFormOf |
P21674
|
FINISHED |
| Object | Maartenszoon |
E112403
|
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: Maartenszoon | Statement: [Maartenszen, isRelatedFormOf, Maartenszoon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maartenszoon Context triple: [Maartenszen, isRelatedFormOf, Maartenszoon]
-
A.
Maartenszen
chosen
Maartenszen is a Dutch patronymic surname indicating "son of Maarten," historically used in the Netherlands.
-
B.
Cornelis
Cornelis is a Dutch given name historically borne by notable figures such as statesman Cornelis de Witt.
-
C.
Jan Willem de Winter
Jan Willem de Winter was a Dutch admiral of the late 18th century, best known for leading the Batavian fleet against the British in the Battle of Camperdown.
-
D.
Pieterszoon
Pieterszoon is a Dutch patronymic surname element meaning "son of Pieter," commonly found in historical Dutch names.
-
E.
Jan Janszoon
Jan Janszoon, better known by the Latinized name Johannes Janssonius, was a prominent 17th-century Dutch cartographer and publisher associated with the influential Blaeu family in Amsterdam.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd72c062d08190b755fa7461839f52 |
completed | March 20, 2026, 4:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be92598ff88190b63a589524180272 |
completed | March 21, 2026, 12:43 p.m. |
Created at: March 20, 2026, 1:34 p.m.