Triple
T1600750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franche-Comté |
E34385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative region of France |
C4506
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former administrative region of France Context triple: [Franche-Comté, instanceOf, former administrative region of France]
-
A.
former province of France
A former province of France is a historical territorial and administrative region that existed before the French Revolution, often retaining distinct cultural and regional identities despite no longer having official administrative status.
-
B.
region of France
chosen
A region of France is a large administrative and territorial division that groups several departments under a common regional government, identity, and economic framework.
-
C.
overseas department and region of France
An overseas department and region of France is a territorial collectivity located outside the European continent that holds the same political status as mainland French departments and regions, fully integrated into the French Republic and the European Union.
-
D.
former French colony
A former French colony is a territory that was once governed or administered by France as part of its overseas empire but has since gained independence or undergone a change in political status.
-
E.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
- F. None of above.
Provenance (1 batch)
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_69a885fdcb9c819081ce6f0b8cd477dd |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.