Triple
T230362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andries van Dam |
E4397
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Andries |
E8082
|
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: Andries | Statement: [Andries van Dam, givenName, Andries]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andries Context triple: [Andries van Dam, givenName, Andries]
-
A.
Andru
Andru is a diminutive form of the given name Andrei, typically used as an affectionate or informal nickname.
-
B.
Willem
Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
-
C.
Andreas
chosen
Andreas is a masculine given name of Greek origin, commonly used in various European and international cultures.
-
D.
Adelbert
Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
-
E.
Johanus
Johanus is a given name, likely a variant or diminutive of Johan, used as a personal first name in some cultures.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25cac7994819080b0b3b10808f8e5 |
completed | Feb. 28, 2026, 3:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3949c6dfc81909a7aaa0ac3e91a65 |
completed | March 1, 2026, 1:21 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.