Triple
T9756465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svein Rosseland |
E236565
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Svein |
E807009
|
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: Svein | Statement: [Svein Rosseland, givenName, Svein]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Svein Context triple: [Svein Rosseland, 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.
Olav Audunssøn
Olav Audunssøn is the conflicted medieval Norwegian nobleman who serves as the central figure in Sigrid Undset’s historical novel cycle "The Master of Hestviken."
-
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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb2889481908fba4a449d5007fe |
completed | April 1, 2026, 10:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1b02ff0f4819080410d4e7e809a24 |
completed | April 5, 2026, 12:43 a.m. |
Created at: March 30, 2026, 8:24 p.m.