Triple
T21294608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svein Knutsson |
E524887
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Svein |
—
|
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: Svein | Statement: [Svein Knutsson, givenName, Svein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svein Context triple: [Svein Knutsson, givenName, Svein]
-
A.
Svein
chosen
Svein is a masculine given name of Old Norse origin, commonly used in Scandinavian countries.
-
B.
Eirik
Eirik is a given name, primarily used in Scandinavian countries, that is a variant of the name Eric.
-
C.
Halvdan
Halvdan is a masculine given name of Scandinavian origin, historically borne by several notable Norwegian figures.
-
D.
Guttorm of Norway
Guttorm of Norway was a short-reigning 12th-century Norwegian king from the House of Sverre who ruled as a child during a turbulent period of civil wars.
-
E.
Ragnfrid
Ragnfrid is a Scandinavian female given name of Old Norse origin, historically used in Norway and other Nordic countries.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73857784881908c3b8418a4c00c1e |
completed | April 21, 2026, 8:41 a.m. |
Created at: April 16, 2026, 4:04 p.m.