Triple

T20624460
Position Surface form Disambiguated ID Type / Status
Subject Lars Frederiksen E506780 entity
Predicate familyName P18 FINISHED
Object Frederiksen 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: Frederiksen | Statement: [Lars Frederiksen, familyName, Frederiksen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frederiksen
Context triple: [Lars Frederiksen, familyName, Frederiksen]
  • A. Frederiksen chosen
    Frederiksen is a common Danish surname borne by various notable figures in Denmark, including politicians, athletes, and artists.
  • B. Friedrichsen
    Friedrichsen is a German-language surname, typically a patronymic meaning "son of Friedrich."
  • C. Thorkildsen
    Thorkildsen is a Norwegian surname borne by various notable individuals across fields such as sports and politics.
  • D. Lindstrøm
    Lindstrøm is a Norwegian surname most notably associated with polar explorer and cook Adolf Henrik Lindstrøm, who took part in several major Arctic and Antarctic expeditions.
  • E. Filskov
    Filskov is a small village in central Jutland, Denmark, known as the birthplace of LEGO founder Ole Kirk Christiansen.
  • 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_69e0b4bc90988190ac360aaf645efc1d completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6abe3d76c8190a8a5cb52bb9bfc2b completed April 20, 2026, 10:42 p.m.
Created at: April 16, 2026, 11:42 a.m.