Triple
T6840750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulrich |
E157565
|
entity |
| Predicate | hasVariantSpelling |
P457
|
FINISHED |
| Object | Ulrik |
E623802
|
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: Ulrik | Statement: [Ulrich, hasVariantSpelling, Ulrik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulrik Context triple: [Ulrich, hasVariantSpelling, Ulrik]
-
A.
Ulrik
chosen
Ulrik is a masculine given name of Scandinavian origin, commonly used in countries like Denmark and Norway and related to the German name Ulrich.
-
B.
Søren
Søren is a masculine given name of Scandinavian origin, most famously borne by the Danish philosopher Søren Kierkegaard.
-
C.
Henrik
Henrik is the given name of the renowned Norwegian mathematician Niels Henrik Abel, known for his pioneering work in algebra and analysis.
-
D.
Johan
Johan is the given first name of the Swedish playwright and novelist August Strindberg.
-
E.
Johan
Johan is a masculine given name of Scandinavian origin, commonly used in countries such as Norway, Sweden, and Denmark.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6b4a1f88190b4f532828697fbd8 |
completed | March 27, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c74271b9dc8190abbe3b1f9819c38f |
completed | March 28, 2026, 2:52 a.m. |
Created at: March 27, 2026, 2:19 p.m.