Triple
T37778275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Município de Santa Maria de Jetibá |
E941749
|
entity |
| Predicate | regiãoImediata |
P67895
|
FINISHED |
| Object | região serrana do Espírito Santo |
—
|
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: região serrana do Espírito Santo | Statement: [Município de Santa Maria de Jetibá, regiãoImediata, região serrana do Espírito Santo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regiãoImediata Context triple: [Município de Santa Maria de Jetibá, regiãoImediata, região serrana do Espírito Santo]
-
A.
locatedInMesoregion
Indicates that an entity is geographically situated within a specific mesoregion.
-
B.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
C.
regionSub
chosen
Indicates that one region is a subregion or contained part of another, larger region.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified 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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbaf45bd40819090879114ec90db3e |
completed | May 6, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.