Triple
T8490662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolaas Tinbergen |
E200959
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Nikolaas |
E682625
|
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: Nikolaas | Statement: [Nikolaas Tinbergen, givenName, Nikolaas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nikolaas Context triple: [Nikolaas Tinbergen, givenName, Nikolaas]
-
A.
Nikolaas
chosen
Nikolaas is a Dutch given name, equivalent to Nicholas, commonly used in the Netherlands and Flanders.
-
B.
Nicolaas
Nicolaas is the given name of the influential Afrikaans poet, playwright, and essayist N. P. van Wyk Louw.
-
C.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
D.
Nicolaus
Nicolaus is a Latin given name of Greek origin, historically borne by various religious figures, scholars, and notable individuals across Europe.
-
E.
Anthonie
Anthonie is a Dutch given name historically borne by notable figures such as statesman Anthonie Heinsius.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55af3f48190a8cd64cdce0ebd4c |
completed | March 31, 2026, 3:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce3a54c3888190b11b7e9909abe518 |
completed | April 2, 2026, 9:43 a.m. |
Created at: March 30, 2026, 6:13 p.m.