Triple
T30554341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Nacional do Caminhão |
E777653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian city epithet |
C48321
|
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: Brazilian city epithet Context triple: [Capital Nacional do Caminhão, instanceOf, Brazilian city epithet]
-
A.
apelido de cidade
chosen
Um apelido de cidade é uma designação informal e popular que sintetiza características marcantes, históricas, culturais ou simbólicas de uma cidade, diferenciando-a de seu nome oficial.
-
B.
administrative region of the Federal District of Brazil
An administrative region of the Federal District of Brazil is a territorial subdivision governed by a regional administration that manages local public services and implements district-level policies within its defined area.
-
C.
municipality of Brazil
A municipality of Brazil is the smallest autonomous administrative division in the country, governed by a mayor and municipal council, responsible for local public services, regulations, and development within its defined territory.
-
D.
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.
-
E.
Latin city
A Latin city is an urban settlement within the ancient Latin cultural and political sphere, typically in Latium, sharing common language, religious practices, and legal-political institutions with Rome and other Latin communities.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:20 p.m.