Triple

T9765351
Position Surface form Disambiguated ID Type / Status
Subject QFO E236973 entity
Predicate locatedIn P40 FINISHED
Object Florennes E236971 NE FINISHED

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: Florennes | Statement: [QFO, locatedIn, Florennes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Florennes
Context triple: [QFO, locatedIn, Florennes]
  • A. Florennes chosen
    Florennes is a municipality in the Wallonia region of Belgium, known for hosting a major military air base and its surrounding rural landscape.
  • B. Les Breuleux
    Les Breuleux is a small Swiss municipality and village in the Jura region, known for its watchmaking tradition and rural alpine setting.
  • C. Seneffe
    Seneffe is a municipality in the province of Hainaut in Wallonia, Belgium, historically notable as the site of a major 17th-century battle during the Franco-Dutch War.
  • D. Fallières
    Fallières is a French surname most notably borne by Armand Fallières, who served as President of France in the early 20th century.
  • E. Flémalle
    Flémalle is a municipality in eastern Belgium known for its industrial heritage and location along the Meuse River in the province of Liège.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca84d831b8819090322686b47887ce completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0a040988190b1c940f9e5c42f9c completed April 1, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bcf965e88190b505ce160f77e9b7 completed April 5, 2026, 1:38 a.m.
Created at: March 30, 2026, 8:25 p.m.