Triple

T15815291
Position Surface form Disambiguated ID Type / Status
Subject Benedict Birgersson E383458 entity
Predicate familyName P18 FINISHED
Object Birgersson E378581 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: Birgersson | Statement: [Benedict Birgersson, familyName, Birgersson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Birgersson
Context triple: [Benedict Birgersson, familyName, Birgersson]
  • A. Birger
    Birger is a Scandinavian male given name of Old Norse origin, traditionally associated with meanings like "helper" or "protector."
  • B. Eric Birgersson chosen
    Eric Birgersson was a 13th-century Swedish prince, son of the influential statesman Birger Jarl, who played a role in the power struggles of medieval Sweden.
  • C. 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."
  • D. Alfredson
    Alfredson is a Swedish surname most notably associated with filmmaker Tomas Alfredson.
  • E. Olof
    Olof is a Scandinavian male given name, particularly common in Sweden and Norway, derived from Old Norse and borne by various notable historical and cultural figures.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0c4a219508190b8588120ec415ac7 completed April 16, 2026, 11:14 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff99959f048190ae24a072387ec233 completed May 9, 2026, 8:31 p.m.
Created at: April 10, 2026, 4:49 a.m.