Triple
T3842005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moselle |
E93471
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Metz |
E90772
|
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: Metz | Statement: [Moselle, capital, Metz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metz Context triple: [Moselle, capital, Metz]
-
A.
Metz
chosen
Metz is a historic city in northeastern France known for its Gothic Saint-Stephen Cathedral, Roman and medieval heritage, and role as the capital of the Moselle department in the Grand Est region.
-
B.
Maubeuge
Maubeuge is a fortified industrial town in northern France near the Belgian border, historically significant for its strategic military position.
-
C.
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.
-
D.
Thionville
Thionville is a town in northeastern France near the Luxembourg border, known historically as a strategic industrial and military center in the Moselle region.
-
E.
Colmar
Colmar is a picturesque historic town in northeastern France’s Alsace region, renowned for its well-preserved medieval and early Renaissance architecture and canals.
- 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_69b613261ca4819087df0e78efc7ba79 |
completed | March 15, 2026, 2:02 a.m. |
Created at: March 9, 2026, 3:18 p.m.