Triple
T12560223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East End of Pittsburgh |
E295322
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Pittsburgh |
C21768
|
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 Pittsburgh Context triple: [East End of Pittsburgh, instanceOf, region of Pittsburgh]
-
A.
township in Pennsylvania
A township in Pennsylvania is a type of municipal subdivision of a county that provides local government services to residents in areas that are typically less densely populated than cities or boroughs.
-
B.
municipality in Pennsylvania
A municipality in Pennsylvania is a legally defined local government entity—such as a city, borough, township, or town—responsible for providing public services and governance within its geographic boundaries in the state of Pennsylvania.
-
C.
county of Pennsylvania
A county of Pennsylvania is an administrative and geographic subdivision of the Commonwealth of Pennsylvania that provides local government services, maintains public records, and serves as a jurisdictional unit for courts, elections, and taxation.
-
D.
region of Austria
A region of Austria is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and natural features.
-
E.
populated place in Allegheny County, Pennsylvania
chosen
A populated place in Allegheny County, Pennsylvania is any city, borough, township, neighborhood, or other community where people live within the geographic boundaries of Allegheny County in the state of Pennsylvania.
- 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 11:48 p.m.