Triple
T14203767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrike |
E352030
|
entity |
| Predicate | hasRelatedName |
P3889
|
FINISHED |
| Object | Henrika |
E352030
|
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: Henrika | Statement: [Henrike, hasRelatedName, Henrika]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Henrika Context triple: [Henrike, hasRelatedName, Henrika]
-
A.
Henrike
chosen
Henrike is a feminine given name of German origin, serving as the female form of Heinrich.
-
B.
Ottilia
Ottilia is a feminine given name of Germanic origin, related to Otto and typically interpreted to mean "wealth" or "prosperity."
-
C.
Hendrika
Hendrika is a feminine given name of Dutch origin, commonly used in the Netherlands and related to the name Hendrickje.
-
D.
Maddalene
Maddalene is a feminine given name, typically considered a variant of Maddalena or Magdalene, with roots in Christian and European naming traditions.
-
E.
Ulrike
Ulrike is a German given name, typically feminine, derived from the name Ulrich and associated with German-speaking countries.
- 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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd1951421c81908959634e66857b61 |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 1:05 a.m.