Triple
T12630034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | historical province of Burgundy |
E301615
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former administrative division of France |
C6761
|
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 division of France Context triple: [historical province of Burgundy, instanceOf, former administrative division of France]
-
A.
former province of France
chosen
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.
former French department
A former French department is an administrative division that once functioned as a territorial unit of governance within France but has since been dissolved, merged, or reorganized.
-
C.
administrative division of France
An administrative division of France is a territorial unit, such as a region, department, arrondissement, canton, or commune, established by the French government to organize local governance, public administration, and the delivery of state services.
-
D.
prefecture of France
A prefecture of France is an administrative center, typically a city, that serves as the seat of the state’s representative (the prefect) and the main government offices for a department or region.
-
E.
district of France
A district of France is an administrative subdivision within a department, historically used to organize local governance, judicial functions, and public administration.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:15 p.m.