Triple
T33794177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seine department |
E866021
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former department of France |
C27252
|
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 department of France Context triple: [Seine department, instanceOf, former department of France]
-
A.
former French department
chosen
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.
department of France
A department of France is an administrative territorial division within the country, situated between the region and commune levels, responsible for local governance, public services, and implementation of national policies.
-
C.
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.
-
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.
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.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:46 a.m.