Triple

T20406780
Position Surface form Disambiguated ID Type / Status
Subject Ordonnance de Moulins E500487 entity
Predicate placeOfIssue P2108 FINISHED
Object Moulins 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: Moulins | Statement: [Ordonnance de Moulins, placeOfIssue, Moulins]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moulins
Context triple: [Ordonnance de Moulins, placeOfIssue, Moulins]
  • A. Moulins chosen
    Moulins is a historic town in central France known for its well-preserved medieval architecture and cultural heritage.
  • B. Sous-Moulin
    Sous-Moulin is a locality within the municipality of Thônex in the canton of Geneva, Switzerland, known primarily as a residential and community area.
  • C. Moulin
    Moulin is a French surname most famously associated with Jean Moulin, a leading figure of the French Resistance during World War II.
  • D. Moulin
    Moulin is a small village near Pitlochry in Perthshire, Scotland, known as a common starting point for hikes up the nearby hill Ben Vrackie.
  • E. Moulin
    Moulin is a French commune known for its cultural and municipal partnership as a twin town of Wesel, Germany.
  • 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_69e0b4a81bec8190b69adfdc1336a015 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67993dc7081908ebd54ec92e712ea completed April 20, 2026, 7:08 p.m.
Created at: April 16, 2026, 11:29 a.m.