Triple

T3841997
Position Surface form Disambiguated ID Type / Status
Subject Moselle E93471 entity
Predicate subprefecture P9697 FINISHED
Object Thionville E58199 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: Thionville | Statement: [Moselle, subprefecture, Thionville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thionville
Context triple: [Moselle, subprefecture, Thionville]
  • A. Thionville chosen
    Thionville is a town in northeastern France near the Luxembourg border, known historically as a strategic industrial and military center in the Moselle region.
  • B. Bar-le-Duc
    Bar-le-Duc is a historic town in northeastern France, known as the former capital of the Duchy of Bar and for its Renaissance architecture and traditional mirabelle plum jam.
  • C. Sarreguemines
    Sarreguemines is a town in northeastern France near the German border, historically known for its ceramics and faience production.
  • D. Sarrebourg
    Sarrebourg is a small historic town in northeastern France known for its cultural heritage and location in the Moselle department of the Grand Est region.
  • E. Maubeuge
    Maubeuge is a fortified industrial town in northern France near the Belgian border, historically significant for its strategic military position.
  • 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_69aed96ce578819084ab16e3439976c9 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeebb397ac81908f74a42a0eeb8682 completed March 9, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5122ba6a4819099986e50f42f2a92 completed March 14, 2026, 7:45 a.m.
Created at: March 9, 2026, 3:18 p.m.