Triple
T37963075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capital Nacional do Calçado |
E947057
|
entity |
| Predicate | tipoDeTopônimo |
P17163
|
FINISHED |
| Object | topônimo promocional |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: topônimo promocional | Statement: [Capital Nacional do Calçado, tipoDeTopônimo, topônimo promocional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeTopônimo Context triple: [Capital Nacional do Calçado, tipoDeTopônimo, topônimo promocional]
-
A.
typeOfToponym
chosen
Indicates the specific category or kind of place name (toponym) that applies to a given geographic entity.
-
B.
onomasticType
Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
-
C.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
D.
UNGEGNToponym
Indicates a standardized geographical name (toponym) as defined or recommended by the United Nations Group of Experts on Geographical Names (UNGEGN).
-
E.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
- F. None of above.
Provenance (3 batches)
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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.