Triple
T35994369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Miami planning districts |
E1040938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative subdivision scheme |
C41870
|
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: administrative subdivision scheme Context triple: [City of Miami planning districts, instanceOf, administrative subdivision scheme]
-
A.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
B.
administrative division collection
chosen
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.
-
C.
hierarchical scheme
A hierarchical scheme is an organized structure in which elements are arranged in multiple levels of increasing or decreasing rank, importance, or inclusiveness, with each level subordinate to the one above it.
-
D.
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.
-
E.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.