Triple
T22220281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bjørn Bjørnson |
E549190
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Bjørn |
—
|
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: Bjørn | Statement: [Bjørn Bjørnson, givenName, Bjørn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bjørn Context triple: [Bjørn Bjørnson, givenName, Bjørn]
-
A.
Bjørn
chosen
Bjørn is a Scandinavian male given name, commonly used in Norway and Denmark and meaning "bear."
-
B.
Torbjørn
Torbjørn is a Scandinavian masculine given name, particularly common in Norway, derived from Old Norse elements meaning "Thor" and "bear."
-
C.
Olaf Rye
Olaf Rye was a 19th-century Norwegian-Danish military officer and national hero, known for his role in the First Schleswig War and celebrated as one of Norway’s early modern war heroes.
-
D.
Ole Einar
Ole Einar is a Norwegian former biathlete widely regarded as one of the greatest in the sport’s history.
-
E.
Jørgen
Jørgen is a Scandinavian male given name, commonly used in Denmark and Norway and related to the name George.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8fa3d081908db0a0556b009d8f |
completed | April 28, 2026, 9:50 p.m. |
Created at: April 16, 2026, 8:37 p.m.