Triple

T16430107
Position Surface form Disambiguated ID Type / Status
Subject Villiers-le-Bel E399048 entity
Predicate locatedNear P294 FINISHED
Object Gonesse 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: Gonesse | Statement: [Villiers-le-Bel, locatedNear, Gonesse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gonesse
Context triple: [Villiers-le-Bel, locatedNear, Gonesse]
  • A. Gonesse chosen
    Gonesse is a commune in the northeastern suburbs of Paris, France, known historically as a rural town and now as part of the greater Paris metropolitan area.
  • B. Crosne
    Crosne is a small suburban commune in the Île-de-France region of northern France, located southeast of Paris.
  • C. Nogent-sur-Seine
    Nogent-sur-Seine is a commune in north-central France known for its riverside setting on the Seine and its proximity to the Nogent-sur-Seine Nuclear Power Plant.
  • D. Étampes
    Étampes is a historic commune and former royal town in northern France, located in the Essonne department in the Île-de-France region.
  • E. Nogent-sur-Oise
    Nogent-sur-Oise is a commune in northern France situated in the Oise department, known for its residential character and proximity to the city of Creil.
  • 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_69d87f2b9024819085c20e52de95d583 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e328fe0f488190ac34aa677c980a20 completed April 18, 2026, 6:47 a.m.
Created at: April 10, 2026, 5:10 a.m.