Triple
T5834837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eirik Kristoffersen |
E129441
|
entity |
| Predicate | givenName |
P17
|
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: [Eirik Kristoffersen, givenName, Eirik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eirik Context triple: [Eirik Kristoffersen, givenName, Eirik]
-
A.
Eirik
chosen
Eirik is a given name, primarily used in Scandinavian countries, that is a variant of the name Eric.
-
B.
Erling
Erling is a masculine given name of Scandinavian origin, commonly used in Norway and other Nordic countries.
-
C.
Geir
Geir is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and meaning "spear."
-
D.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
E.
Ingvar
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 (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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c034a1e6a88190b1aac05511793315 |
completed | March 22, 2026, 6:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0a196ebb88190aea57899be954aae |
completed | March 23, 2026, 2:12 a.m. |
Created at: March 22, 2026, 3:54 p.m.