Triple
T8061812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodoor Rombouts |
E188140
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Theodoor |
E270316
|
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: Theodoor | Statement: [Theodoor Rombouts, givenName, Theodoor]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Theodoor Context triple: [Theodoor Rombouts, givenName, Theodoor]
-
A.
Teodoor
chosen
Teodoor is a given name variant of Theodore, typically used in certain European languages or contexts.
-
B.
Adriaan
Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
-
C.
Gerhardus
Gerhardus is a masculine given name of Germanic origin, closely related to names like Gerhard and Gerard, typically meaning “strong with the spear” or “brave with the spear.”
-
D.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
E.
Constantijn
Constantijn is a Dutch royal, the youngest son of former Queen Beatrix and brother of King Willem-Alexander of the Netherlands.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcd7bcc8190b0a629a813846f13 |
completed | March 31, 2026, 3:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc63da3bd08190894b2f4c977167c0 |
completed | April 1, 2026, 12:16 a.m. |
Created at: March 30, 2026, 5:26 p.m.