Triple
T15196248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirck van Baburen |
E363144
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Baburen |
E363144
|
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: van Baburen | Statement: [Dirck van Baburen, familyName, van Baburen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Baburen Context triple: [Dirck van Baburen, familyName, van Baburen]
-
A.
van Baburen
chosen
Van Baburen is the surname of Dirck van Baburen, a Dutch Golden Age painter known for his Caravaggesque style and genre scenes.
-
B.
van Beinum
Van Beinum is a Dutch surname most notably associated with Eduard van Beinum, the renowned mid-20th-century conductor of the Royal Concertgebouw Orchestra.
-
C.
Gogolin
Gogolin is a small town in southwestern Poland known for its Silesian cultural heritage and location within the Opole region.
-
D.
Totleben
Totleben is a German-origin surname most notably associated with Eduard Totleben, a prominent 19th-century Russian military engineer and general.
-
E.
Vasishka
Vasishka was a Kushan emperor who ruled parts of northern India and Central Asia in the early 3rd century CE, known primarily from his inscriptions and coinage.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067fcc788190abdc083d4eadeb36 |
completed | April 15, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed3324fdc8190b31d4d2fcaffc57a |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 10, 2026, 3:10 a.m.