Triple
T20328040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vilhelm Bohr |
E492392
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bohr |
E405625
|
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: Bohr | Statement: [Vilhelm Bohr, familyName, Bohr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bohr Context triple: [Vilhelm Bohr, familyName, Bohr]
-
A.
Bohr
chosen
Bohr is a prominent Danish surname most famously associated with physicist Niels Bohr and mathematician Harald Bohr.
-
B.
Niels Bohr
Niels Bohr was a pioneering Danish physicist whose model of the atom and foundational work in quantum theory profoundly shaped modern physics.
-
C.
Vilhelm Bohr
Vilhelm Bohr is a Danish physicist and biophysicist known for his research in neurodegenerative diseases and for being part of the prominent Bohr scientific family.
-
D.
Ernest Bohr
Ernest Bohr was a Danish lawyer and Olympic field hockey player, and the son of Nobel Prize–winning physicist Niels Bohr.
-
E.
Erik Bohr
Erik Bohr is a person who shares the notable surname associated with the famous physicist Niels Bohr.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e513608190b70527cd9f4d5da3 |
completed | April 20, 2026, 7 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08612f90b08190a6b700906944fc27 |
completed | May 16, 2026, 12:21 p.m. |
Created at: April 16, 2026, 11:21 a.m.