Triple

T7563464
Position Surface form Disambiguated ID Type / Status
Subject Moulins Cathedral E178849 entity
Predicate locatedIn P40 FINISHED
Object Moulins E29623 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: Moulins | Statement: [Moulins Cathedral, locatedIn, Moulins]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moulins
Context triple: [Moulins Cathedral, locatedIn, 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 commune known for its cultural and municipal partnership as a twin town of Wesel, Germany.
  • D. Moulin
    Moulin is a French surname most famously associated with Jean Moulin, a leading figure of the French Resistance during World War II.
  • E. Champ-du-Moulin
    Champ-du-Moulin is a small hamlet in the Areuse gorge in the canton of Neuchâtel, Switzerland, known for its scenic river landscape and hiking trails.
  • 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_69c69f2f80288190b95cceb4da92ab2b completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f8fb1c00819096bdb73334d8d72e completed March 27, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69c8a2083fdc8190b44e84e02ac3ef0a completed March 29, 2026, 3:52 a.m.
Created at: March 27, 2026, 3:50 p.m.