Triple
T9971813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernhards |
E196224
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Bernhard |
E38564
|
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: Bernhard | Statement: [Bernhards, hasSpellingVariant, Bernhard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bernhard Context triple: [Bernhards, hasSpellingVariant, Bernhard]
-
A.
Bernhard
chosen
Bernhard is a male given name of Germanic origin, historically borne by various European nobles and royals, including Prince Bernhard of the Netherlands.
-
B.
Benno
Benno is a masculine given name, used as a variant or extended form of the name Ben in various European languages.
-
C.
Bernharda
Bernharda is a feminine given name, primarily used in Central and Eastern Europe, derived from the masculine name Bernhard.
-
D.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
-
E.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7bb03688190a3f4fc1988b8fafa |
completed | April 2, 2026, 12:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2cb77b51481908af779b8ecacc3f1 |
completed | April 5, 2026, 8:52 p.m. |
Created at: March 30, 2026, 8:48 p.m.