Triple
T25411830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Phoenix |
E636720
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Phoenix |
C28946
|
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: region of Phoenix Context triple: [East Phoenix, instanceOf, region of Phoenix]
-
A.
county of Arizona
A county of Arizona is a primary local government and administrative division within the state of Arizona, responsible for regional services such as law enforcement, courts, public records, and infrastructure across its defined geographic area.
-
B.
subregion of metropolitan area
chosen
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.
-
C.
Yavapai group
The Yavapai group is a conceptual class representing a collection of related entities, individuals, or data elements associated with the Yavapai people, culture, or region, treated as a single organized unit for classification or analysis.
-
D.
region of Seattle
A region of Seattle represents a specific geographic area within the city, defined by boundaries and associated with particular neighborhoods, landmarks, and administrative or cultural characteristics.
-
E.
subregion of Los Angeles County
A subregion of Los Angeles County is a geographically defined portion of the county characterized by shared social, economic, cultural, or environmental features used for planning, governance, and analysis.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 1:55 p.m.