Triple
T22950399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banlieues 89 |
E569997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French public policy program |
C31667
|
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 policy program Context triple: [Banlieues 89, instanceOf, French public policy program]
-
A.
French government program
chosen
A French government program is an organized set of public policies, measures, and resources implemented by the French state to achieve specific social, economic, cultural, or environmental objectives.
-
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.
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.
-
D.
French political organisation
A French political organisation is a structured group operating within France’s political system to influence public policy, represent interests, or compete for governmental power in accordance with French law and institutions.
-
E.
Swedish government program
A Swedish government program is an organized set of publicly funded initiatives and measures implemented by Swedish authorities to achieve specific social, economic, or environmental policy goals.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:46 p.m.