Triple
T6160804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nossa Senhora do Socorro |
E137435
|
entity |
| Predicate | regionalLocationWithinState |
P69120
|
FINISHED |
| Object | eastern Sergipe |
—
|
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: eastern Sergipe | Statement: [Nossa Senhora do Socorro, regionalLocationWithinState, eastern Sergipe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalLocationWithinState Context triple: [Nossa Senhora do Socorro, regionalLocationWithinState, eastern Sergipe]
-
A.
locatedInCountyRegion
Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
-
B.
countyRegion
Indicates that a county is located within, or is administratively part of, a larger geographic region.
-
C.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
D.
locatedInUnion
Indicates that an entity is situated within or is a member of a specific union or collective grouping.
-
E.
refersToStateInRegion
Indicates that one entity denotes or references a specific state located within a particular region.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d35b2f88190abb9b90b5971e6d7 |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.