Triple
T31340935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cidade Universitária |
E799302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood of Rio de Janeiro |
C8815
|
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: neighborhood of Rio de Janeiro Context triple: [Cidade Universitária, instanceOf, neighborhood of Rio de Janeiro]
-
A.
bairro of Rio de Janeiro
chosen
A bairro of Rio de Janeiro is an officially defined urban neighborhood that serves as a basic territorial, social, and administrative unit within the city, characterized by its own local identity, infrastructure, and community life.
-
B.
zone of Rio de Janeiro
A zone of Rio de Janeiro is a major administrative and geographic subdivision of the city that groups together multiple neighborhoods sharing similar urban, social, and economic characteristics.
-
C.
administrative zone of Rio de Janeiro
An administrative zone of Rio de Janeiro is a territorial subdivision of the city used by the municipal government to organize and manage public services, planning, and administration across different urban regions.
-
D.
road in Rio de Janeiro
A road in Rio de Janeiro is a public thoroughfare within the city’s urban or suburban area that facilitates vehicular and pedestrian movement while connecting neighborhoods, landmarks, and infrastructure across Rio’s diverse topography.
-
E.
sector of Tijuca National Park
A sector of Tijuca National Park is a defined management and geographic subdivision of the park, characterized by specific natural features, conservation objectives, and permitted public uses.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:16 p.m.