Triple

T21550732
Position Surface form Disambiguated ID Type / Status
Subject Église Saint-Martin de Nolay E531753 entity
Predicate locatedIn P40 FINISHED
Object Nolay 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: Nolay | Statement: [Église Saint-Martin de Nolay, locatedIn, Nolay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nolay
Context triple: [Église Saint-Martin de Nolay, locatedIn, Nolay]
  • A. Nolay chosen
    Nolay is a small historic commune in eastern France’s Côte-d'Or department, known for its medieval architecture and traditional Burgundy wine culture.
  • B. Noville
    Noville is a small Swiss municipality in the canton of Vaud, situated near the eastern end of Lake Geneva and known for its natural wetlands and rural character.
  • C. Groslay
    Groslay is a small suburban commune in the Val-d'Oise department in northern France, forming part of the Paris metropolitan area.
  • D. Maringe
    Maringe is an alternate name for the Cheke Holo language spoken in the Solomon Islands.
  • E. Marloie
    Marloie is a village in the Walloon region of Belgium known for its railway station on the Brussels–Luxembourg line.
  • 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_69e0c460232c81908de2c3819d17c00e completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eeb59258b88190966c18f1f519dad6 completed April 27, 2026, 1:02 a.m.
Created at: April 16, 2026, 6:28 p.m.