Triple
T251213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reedy Creek Improvement District |
E5150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former special district |
C536
|
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 special district Context triple: [Reedy Creek Improvement District, instanceOf, former special district]
-
A.
former administrative territorial entity
chosen
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
federal district
A federal district is a distinct territorial unit under the direct jurisdiction of a national government, separate from any constituent state or province, typically established to house the nation's capital or serve special administrative purposes.
-
C.
former political institution
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
D.
Los Angeles City Council district
A Los Angeles City Council district is a geographically defined electoral area within the City of Los Angeles, each represented by a single councilmember responsible for local legislation, constituent services, and community advocacy.
-
E.
public school district
A public school district is a government-funded administrative entity responsible for managing and operating a group of public schools within a defined geographic area.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.