Triple
T32395664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conceição de Macabu |
E827798
|
entity |
| Predicate | stateIsoCode |
P20781
|
FINISHED |
| Object | BR-RJ |
—
|
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: BR-RJ | Statement: [Conceição de Macabu, stateIsoCode, BR-RJ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateIsoCode Context triple: [Conceição de Macabu, stateIsoCode, BR-RJ]
-
A.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
B.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
C.
stateName
Indicates that an entity is identified by or associated with a particular state’s name.
-
D.
stateSubdivisionCode
chosen
Indicates the standardized code that identifies a specific subdivision (such as a state, province, or region) within a larger country or territory.
-
E.
provinceState
Indicates that one entity is a province or state that is administratively contained within or associated with another, typically larger, territorial entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 12:52 a.m.