Triple
T25133191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saône-et-Loire departmental territory |
E629584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French departmental territory |
C27207
|
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: French departmental territory Context triple: [Saône-et-Loire departmental territory, instanceOf, French departmental territory]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
administrative division of France
chosen
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.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.