Triple
T28930177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feira de Santana |
E733758
|
entity |
| Predicate | populationRankInBahia |
P180513
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Feira de Santana, populationRankInBahia, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInBahia Context triple: [Feira de Santana, populationRankInBahia, 2]
-
A.
urbanAreaRankInBrazil
Indicates the relative position or ranking of an urban area compared to other urban areas within Brazil.
-
B.
significantPopulationInBrazilianState
Indicates that a population group or entity has a notably large or important presence within a specific Brazilian state.
-
C.
largestPopulationInBrazilianState
Indicates that the subject has the largest population among all entities within a specified Brazilian state.
-
D.
populationRankInPortugal
Indicates the relative position of an entity in terms of population size compared to other entities within Portugal.
-
E.
populationRankInPuertoRico
Indicates the relative position of a place in terms of population size compared to other places within Puerto Rico.
- F. None of above. chosen
Provenance (4 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 8:27 a.m.