Triple

T13245034
Position Surface form Disambiguated ID Type / Status
Subject Mary de Monthermer E315378 entity
Predicate familyName P18 FINISHED
Object de Monthermer E954393 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: de Monthermer | Statement: [Mary de Monthermer, familyName, de Monthermer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: de Monthermer
Context triple: [Mary de Monthermer, familyName, de Monthermer]
  • A. de Monthermer chosen
    De Monthermer is an English noble family name historically associated with medieval barons and the aristocracy.
  • B. de Montferrand
    de Montferrand is the French noble family name borne by architect Auguste de Montferrand, renowned for designing Saint Isaac's Cathedral in Saint Petersburg.
  • C. Baron Monthermer
    Baron Monthermer was an English peerage title of the late 13th and early 14th centuries associated with the nobleman Ralph de Monthermer and his descendants.
  • D. Le Joly
    Le Joly was a French ship associated with the 17th-century explorer René-Robert Cavelier, Sieur de La Salle, used during his expeditions in North America.
  • E. Leschenault de La Tour
    Leschenault de La Tour was a French botanist and explorer after whom Western Australia’s Leschenault Inlet is named.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d5b06148190a44e698bbe5cd529 completed April 10, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ff3600388190a7f61370f54d5e63 completed May 3, 2026, 7:54 a.m.
Created at: April 9, 2026, 9:23 p.m.