Triple
T23365230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birger of Sweden |
E593297
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Birger |
—
|
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: Birger | Statement: [Birger of Sweden, givenName, Birger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Birger Context triple: [Birger of Sweden, givenName, Birger]
-
A.
Birger
chosen
Birger is a Scandinavian male given name of Old Norse origin, traditionally associated with meanings like "helper" or "protector."
-
B.
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."
-
C.
Bertil
Bertil is a Scandinavian male given name, historically borne by nobility such as the Duke of Halland.
-
D.
Eskil
Eskil is a town and district in central Turkey known for its location within Aksaray Province on the Central Anatolian plateau.
-
E.
Thorkild
Thorkild is a Scandinavian masculine given name of Old Norse origin, traditionally used in Denmark and Norway.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ab7fc481908b496ec9b543eddd |
completed | April 29, 2026, 6:09 a.m. |
Created at: April 17, 2026, 5:31 p.m.