Triple
T11409375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerrik |
E270326
|
entity |
| Predicate | sharesEtymologicalRootsWith |
P28322
|
FINISHED |
| Object | Eirik |
E270325
|
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: Eirik | Statement: [Jerrik, sharesEtymologicalRootsWith, Eirik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eirik Context triple: [Jerrik, sharesEtymologicalRootsWith, Eirik]
-
A.
Eirik
chosen
Eirik is a given name, primarily used in Scandinavian countries, that is a variant of the name Eric.
-
B.
Svein
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
C.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
D.
Erling
Erling is a masculine given name of Scandinavian origin, commonly used in Norway and other Nordic countries.
-
E.
Aasmund
Aasmund is a masculine given name of Norwegian origin, notably borne by the 19th-century writer and journalist Aasmund Olavsson Vinje.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d808855a7481909314f90ad92aae68 |
completed | April 9, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5e8d6392881908fd33d340f3334e7 |
completed | April 20, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:34 p.m.