Triple
T23666830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canindé de São Francisco |
E584600
|
entity |
| Predicate | admDivisionOf |
P69939
|
FINISHED |
| Object | state of Sergipe |
—
|
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: state of Sergipe | Statement: [Canindé de São Francisco, admDivisionOf, state of Sergipe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: admDivisionOf Context triple: [Canindé de São Francisco, admDivisionOf, state of Sergipe]
-
A.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
B.
regionDivision
Indicates a hierarchical or organizational subdivision relationship where one region is partitioned into smaller constituent regions.
-
C.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
D.
isPartOfDivision
Indicates that one entity belongs to, or is contained within, a specific division of a larger organizational or structural unit.
-
E.
subdivisionOfJurisdiction
chosen
Indicates that one jurisdiction is a smaller administrative or territorial unit that forms part of a larger jurisdiction.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40c48088190a61e9a73919bace5 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.