Triple
T20679586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingvar |
E508254
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Yngvarr |
—
|
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: Yngvarr | Statement: [Ingvar, derivedFrom, Yngvarr]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yngvarr Context triple: [Ingvar, derivedFrom, Yngvarr]
-
A.
Erlingr
Erlingr is a variant form of the Scandinavian given name Erling, traditionally associated with Norse and Germanic origins.
-
B.
Svein
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
C.
Eirik
Eirik is a given name, primarily used in Scandinavian countries, that is a variant of the name Eric.
-
D.
Eyvind
Eyvind is a masculine given name of Old Norse origin, historically associated with Scandinavian culture and borne by figures such as the American artist Eyvind Earle.
-
E.
Ingvar
chosen
Ingvar is a Scandinavian given name of Old Norse origin, historically associated with Viking-age figures and meaning roughly "Ing’s warrior" or "warrior of the god Ing."
- 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_69e0b4c1164881909a3bf1e3ddb2bc32 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6bea516b88190b3e90d03fa981a44 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 11:44 a.m.