Triple

T23338199
Position Surface form Disambiguated ID Type / Status
Subject Charles III of France E591656 entity
Predicate spouse P13 FINISHED
Object Frederuna 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: Frederuna | Statement: [Charles III of France, spouse, Frederuna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Frederuna
Context triple: [Charles III of France, spouse, Frederuna]
  • A. Frederuna chosen
    Frederuna was a 10th-century Frankish queen consort of West Francia as the first wife of King Charles the Simple.
  • B. Freirina
    Freirina is a small town and commune in northern Chile known for its agricultural activity and historic architecture within the Atacama Region.
  • C. Albreda
    Albreda is a historic riverside settlement in The Gambia that served as a key trading post and focal point in the transatlantic slave trade.
  • D. Byaelva
    Byaelva is a river located in the Innherad district of Trøndelag county in central Norway.
  • E. Turnesa
    Turnesa is the surname of a prominent American golfing family that produced several notable professional golfers in the early to mid-20th century.
  • 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_69e25d20156c81908c5c53195bd9c738 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1983099188190a2e05cf81d62a641 completed April 29, 2026, 5:33 a.m.
Created at: April 17, 2026, 5:17 p.m.