Triple
T2470243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunnar Birkerts |
E55353
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gunnar |
E30461
|
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: Gunnar | Statement: [Gunnar Birkerts, givenName, Gunnar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gunnar Context triple: [Gunnar Birkerts, givenName, Gunnar]
-
A.
Gunnar
chosen
Gunnar is a masculine given name of Old Norse origin, commonly used in Scandinavian countries and associated with warriors or bold fighters.
-
B.
Ivar
Ivar is a masculine given name of Old Norse origin, traditionally used in Scandinavian countries.
-
C.
Ragnar
Ragnar is a masculine given name of Old Norse origin, historically associated with Viking-age Scandinavia and later borne by various notable figures.
-
D.
Bror
Bror is a given name, notably used as one of the personal names of Swedish musician and ABBA member Benny Andersson.
-
E.
Jarl
Jarl is a masculine given name of Scandinavian origin, historically associated with nobility and leadership.
- 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_69ab49e3622c8190ad22afa2c4fbb807 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd135c64881908cccde3317d14b67 |
completed | March 7, 2026, 7:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af17a29c2c8190b9e7b49d086ad9d5 |
completed | March 9, 2026, 6:55 p.m. |
Created at: March 6, 2026, 9:44 p.m.