Triple
T26929324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ave Subregion |
E678169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative subregion |
C740
|
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 subregion Context triple: [Ave Subregion, instanceOf, administrative subregion]
-
A.
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.
-
B.
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.
-
C.
administrative territorial entity
chosen
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
D.
administrativeDistrictName
The administrativeDistrictName class represents the official name assigned to a specific administrative district within a governmental or organizational territorial hierarchy.
-
E.
subregion of metropolitan area
A subregion of a metropolitan area is a geographically or functionally distinct part of a larger urban region, characterized by shared land use, demographics, infrastructure, or economic activity.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:11 a.m.