Triple
T1490554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Dam |
E29567
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Van Dam |
E29567
|
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 Dam | Statement: [van Dam, hasVariant, Van Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Van Dam Context triple: [van Dam, hasVariant, Van Dam]
-
A.
van Dam
chosen
van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
-
B.
De Dam
De Dam is Amsterdam’s central and historic main square, known for its royal palace, national monument, and role as a major public gathering place.
-
C.
Soesterberg
Soesterberg is a village in the Dutch province of Utrecht known for its historic military air base and long-standing association with the Royal Netherlands Air Force.
-
D.
Van der Madeweg
Van der Madeweg is a metro station in Amsterdam that serves as a stop on the city's rapid transit network.
-
E.
Leven
Leven is a coastal town in eastern Scotland, situated on the Firth of Forth in the council area of Fife.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6c233ec819087e1233af02aabfc |
completed | March 1, 2026, 11:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad1ca98e64819097916eb7717e6364 |
completed | March 8, 2026, 6:52 a.m. |
Created at: March 1, 2026, 8:12 p.m.