Triple
T8490645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Tinbergen |
E200959
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Tinbergen |
E200959
|
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: Tinbergen | Statement: [Jan Tinbergen, familyName, Tinbergen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tinbergen Context triple: [Jan Tinbergen, familyName, Tinbergen]
-
A.
Tinbergen
chosen
Tinbergen is a Dutch surname most famously associated with brothers Jan and Niko Tinbergen, who were pioneering figures in economics and ethology respectively.
-
B.
Westerveld
Westerveld is a rural municipality in the Dutch province of Drenthe, known for its natural landscapes, historic villages, and prehistoric dolmens.
-
C.
Scherpenzeel
Scherpenzeel is a small Dutch municipality in the province of Gelderland, known for its rural character and historic village center.
-
D.
Tubbergen
Tubbergen is a rural municipality and village in the eastern Netherlands, located in the Twente region of the province of Overijssel.
-
E.
Landsmeer
Landsmeer is a small Dutch town and municipality in North Holland, situated just north of Amsterdam and known for its watery landscapes and nature reserves.
- 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.