Triple
T24161930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainha da Borborema |
E598862
|
entity |
| Predicate | localizadaNaRegiao |
P64798
|
FINISHED |
| Object | Agreste paraibano |
—
|
NE NERFINISHED |
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: Agreste paraibano | Statement: [Rainha da Borborema, localizadaNaRegiao, Agreste paraibano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localizadaNaRegiao Context triple: [Rainha da Borborema, localizadaNaRegiao, Agreste paraibano]
-
A.
locatedInMesoregion
Indicates that an entity is geographically situated within a specific mesoregion.
-
B.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
E.
locatedInTraditionalRegion
Indicates that an entity is situated within a specific traditional or historically recognized region.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e9cd6c81908c33242f19fcc034 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:32 p.m.