Triple

T19766567
Position Surface form Disambiguated ID Type / Status
Subject Belleville Bulls E474772 entity
Predicate homeCity P263 FINISHED
Object Belleville 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: Belleville | Statement: [Belleville Bulls, homeCity, Belleville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belleville
Context triple: [Belleville Bulls, homeCity, Belleville]
  • A. Belleville
    Belleville is a vibrant, historically working-class neighborhood in northeastern Paris known for its multicultural character, street art, and lively food scene.
  • B. Belleville
    Belleville is a small village in south-central Wisconsin, known for its rural character and proximity to the Madison metropolitan area.
  • C. Belleville chosen
    Belleville is a small Canadian city in southeastern Ontario, known as a regional service and commercial hub on the Bay of Quinte.
  • D. Belleville valley
    Belleville valley is a geographical valley region whose waters are collected and carried away by the Doron de Belleville river in the French Alps.
  • E. Saint‑Cloud
    Saint-Cloud is a western suburb of Paris, France, historically notable for its royal château and as the site of key political events during the French Revolution and Napoleonic era.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e653232e508190a7d484c0a1e2939a completed April 20, 2026, 4:24 p.m.
Created at: April 10, 2026, 1:48 p.m.