Triple
T16533786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igor |
E401633
|
entity |
| Predicate | derivedFrom |
P909
|
FINISHED |
| Object | Ingvar |
E508254
|
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: Ingvar | Statement: [Igor, derivedFrom, Ingvar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ingvar Context triple: [Igor, derivedFrom, Ingvar]
-
A.
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."
-
B.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
C.
Svein
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
D.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
E.
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.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32eda42548190be61efb25a44a554 |
completed | April 18, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006093244081909ae74674de966d6d |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:15 a.m.