Triple

T18277933
Position Surface form Disambiguated ID Type / Status
Subject Grens E437785 entity
Predicate hasNeighboringMunicipality P224 FINISHED
Object Eysins 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: Eysins | Statement: [Grens, hasNeighboringMunicipality, Eysins]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eysins
Context triple: [Grens, hasNeighboringMunicipality, Eysins]
  • A. Eysins chosen
    Eysins is a small municipality in the canton of Vaud in western Switzerland, situated near the town of Nyon and close to Lake Geneva.
  • B. Beaufays
    Beaufays is a village in the municipality of Chaudfontaine in the province of Liège, Belgium.
  • C. Neuville
    Neuville is a small riverside municipality in the Capitale-Nationale region of Quebec, Canada, known for its historic charm and agricultural landscape along the St. Lawrence River.
  • D. Embourg
    Embourg is a district of the municipality of Chaudfontaine in the province of Liège, Belgium, known as a residential suburb of the city of Liège.
  • E. Finnebach
    Finnebach is a small river in Germany that serves as a tributary of the Unstrut.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50053cc808190b46a3ec9d96936fe completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:34 a.m.