Triple
T15989297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roelof Botha |
E387781
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Roelof |
E959843
|
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: Roelof | Statement: [Roelof Botha, givenName, Roelof]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Roelof Context triple: [Roelof Botha, givenName, Roelof]
-
A.
Roelof
chosen
Roelof is a masculine given name of Dutch origin, commonly used in the Netherlands and among Afrikaans speakers.
-
B.
Marthinus
Marthinus is a masculine given name of Afrikaans and Dutch origin, historically borne by several notable South African figures.
-
C.
Lourens
Lourens is a given name derived from the Latin name Laurentius, commonly used in Dutch and Afrikaans contexts.
-
D.
Hendrik
Hendrik is a masculine given name of Germanic origin, commonly used in Dutch- and German-speaking countries and related to the name Henry.
-
E.
Roelof Vos
Roelof Vos is a Dutch aerospace engineer and academic known for his work in aircraft design and aerodynamics.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157829ec08190aa4a683e29a0148a |
completed | April 16, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3d2369081909efa2d4addf0cf2d |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:54 a.m.