Triple
T1270595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of State of France |
E15699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French public institution |
C1433
|
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 public institution Context triple: [Council of State of France, instanceOf, French public institution]
-
A.
French administrative institution
chosen
A French administrative institution is a public body or authority established by the French state or local governments to implement laws, deliver public services, and manage administrative functions within the framework of French public law.
-
B.
French public agency network
A French public agency network is an interconnected system of government-funded organizations that collaborate to deliver public services, implement national policies, and coordinate administrative actions across France.
-
C.
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.
-
D.
French public official
A French public official is an individual who holds a position of authority or responsibility within France’s governmental or administrative institutions, tasked with implementing public policies and serving the interests of the state and its citizens.
-
E.
region of France
A region of France is a large administrative and territorial division that groups several departments under a common regional government, identity, and economic framework.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.