Triple

T21775816
Position Surface form Disambiguated ID Type / Status
Subject Prince Gustaf, Duke of Uppland E537571 entity
Predicate given name P17 FINISHED
Object Gustaf 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: Gustaf | Statement: [Prince Gustaf, Duke of Uppland, given name, Gustaf]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gustaf
Context triple: [Prince Gustaf, Duke of Uppland, given name, Gustaf]
  • A. Gustaf chosen
    Gustaf is the given name of Carl Gustaf Emil Mannerheim, the Finnish military leader and statesman who served as Commander-in-Chief during World War II and later as President of Finland.
  • B. Ludvig
    Ludvig is a given name, primarily used in Scandinavian countries, that is a variant spelling of Ludwig.
  • C. Gustav
    Gustav is a masculine given name of German origin, borne by several notable historical figures including scientists, artists, and royalty.
  • D. 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.
  • E. Gustav of Vasaborg
    Gustav of Vasaborg was a 17th-century Swedish nobleman and illegitimate son of King Gustavus Adolphus, who was later made Count of Nystad.
  • 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_69e0c470759c819094a215757113562b completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f046291d808190b5111a8d4819909f completed April 28, 2026, 5:31 a.m.
Created at: April 16, 2026, 6:51 p.m.