Triple

T18132800
Position Surface form Disambiguated ID Type / Status
Subject Prince Joachim of Denmark E434055 entity
Predicate title P38 FINISHED
Object Count of Monpezat 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: Count of Monpezat | Statement: [Prince Joachim of Denmark, title, Count of Monpezat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Count of Monpezat
Context triple: [Prince Joachim of Denmark, title, Count of Monpezat]
  • A. Count of Monpezat chosen
    Count of Monpezat is a hereditary French noble title associated with the Danish royal family, notably borne by Prince Frederik of Denmark.
  • B. Monpezat
    Monpezat is a French noble family name associated with Prince Henrik of Denmark and his descendants.
  • C. Pas de Peyrol
    Pas de Peyrol is a high mountain pass in France’s Massif Central, known as the highest road pass in the Cantal department and a key access point to the Puy Mary.
  • D. Roquebillière
    Roquebillière is a small commune in southeastern France, situated in the Alpes-Maritimes department in the Provence-Alpes-Côte d’Azur region.
  • E. Count of Bigorre
    The Count of Bigorre was a medieval noble title associated with the rulers of the County of Bigorre in the Pyrenees region of southwestern France.
  • 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_69d8b909e8cc81908df4cc2b8ea6d11f completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de04321c81909c0b9d47757720fd completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:29 a.m.