Triple
T19840266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collectivity of Corsica |
E476707
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region-level administrative division |
C2248
|
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: region-level administrative division Context triple: [Collectivity of Corsica, instanceOf, region-level administrative division]
-
A.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
-
B.
Second-level administrative division
A second-level administrative division is a territorial unit within a country that is directly below the primary (first-level) administrative regions, such as provinces or states, and typically manages local governance and public services.
-
C.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
D.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
E.
administrative division collection
A collection of administrative divisions is an organized grouping of territorial units (such as states, provinces, or districts) that together represent a structured subdivision of a larger political or geographic entity.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.