Triple
T20656661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leon Van Hove |
E507643
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Van Hove |
—
|
NE NERFINISHED |
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 Hove | Statement: [Leon Van Hove, familyName, Van Hove]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Van Hove Context triple: [Leon Van Hove, familyName, Van Hove]
-
A.
Vandevelde
Vandevelde is a surname of Dutch or Flemish origin, commonly found in Belgium and the Netherlands.
-
B.
Van der Elst
Van der Elst is a Dutch-origin surname commonly found in Belgium and the Netherlands, associated with several notable figures in sports, politics, and the arts.
-
C.
Verhaegen
Verhaegen is a Dutch-language surname of Belgian and Dutch origin, borne by various notable figures in politics, academia, and the arts.
-
D.
Lovaart
Lovaart is a canalized waterway in western Belgium that serves as a branch of the Yser River, used primarily for drainage and local navigation.
-
E.
Leon Van Hove
chosen
Leon Van Hove was a Belgian theoretical physicist known for his pioneering work in quantum field theory and statistical mechanics, including the introduction of Van Hove singularities in solid-state physics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ed48308190b9350a323b9a7952 |
completed | April 20, 2026, 11:12 p.m. |
Created at: April 16, 2026, 11:43 a.m.