Triple

T23161413
Position Surface form Disambiguated ID Type / Status
Subject Rhode-Saint-Genèse E578594 entity
Predicate borderedBy P224 FINISHED
Object Drogenbos 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: Drogenbos | Statement: [Rhode-Saint-Genèse, borderedBy, Drogenbos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Drogenbos
Context triple: [Rhode-Saint-Genèse, borderedBy, Drogenbos]
  • A. Drogenbos chosen
    Drogenbos is a small municipality in the Flemish Brabant province of Belgium, located just southwest of Brussels.
  • B. Dabok
    Dabok is a locality near Udaipur in Rajasthan, India, known primarily for hosting Maharana Pratap Airport, the main air gateway to the region.
  • C. Bosha
    Bosha is an alternative name for the Lom people, a Romani-related ethnic group primarily found in the Caucasus region.
  • D. Steenwerck
    Steenwerck is a commune in northern France’s Nord department, known for its rural character and location near the Belgian border.
  • E. Bogoso
    Bogoso is a mining town in southwestern Ghana known for its significant gold deposits and related industrial activities.
  • 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_69e245fc75348190a0288401044c8af8 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18f006930819097aafef87405d737 completed April 29, 2026, 4:54 a.m.
Created at: April 17, 2026, 4:02 p.m.