Triple

T13632558
Position Surface form Disambiguated ID Type / Status
Subject Pierre Jeanneret E325758 entity
Predicate familyName P18 FINISHED
Object Jeanneret E325758 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: Jeanneret | Statement: [Pierre Jeanneret, familyName, Jeanneret]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jeanneret
Context triple: [Pierre Jeanneret, familyName, Jeanneret]
  • A. Jeanneret chosen
    Jeanneret is a Swiss surname most notably associated with architect Pierre Jeanneret, a key collaborator of Le Corbusier in modernist architecture.
  • B. Jacquère
    Jacquère is a light, crisp white wine grape variety primarily grown in the Alpine regions of eastern France, known for producing fresh, mineral-driven wines.
  • C. Aspremont
    Aspremont is a small picturesque commune in southeastern France, situated in the hills above Nice in the Alpes-Maritimes department.
  • D. Breuillet
    Breuillet is a commune in the Essonne department in the Île-de-France region of northern France.
  • E. Lebrun
    Lebrun is a French surname borne by various notable figures in politics, arts, and other fields.
  • 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_69d8076beddc8190a53156f5bea77f5e completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbc5a490508190924ac40f1dd519d6 completed April 12, 2026, 4:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77fab07648190b3b3362a8ffa8961 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:51 p.m.