Triple
T23498459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil–Bolivia border region |
E571767
|
entity |
| Predicate | hasMajorCityOnBorder |
P15361
|
FINISHED |
| Object | Corumbá |
—
|
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: Corumbá | Statement: [Brazil–Bolivia border region, hasMajorCityOnBorder, Corumbá]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCityOnBorder Context triple: [Brazil–Bolivia border region, hasMajorCityOnBorder, Corumbá]
-
A.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
-
B.
countryBordering
Indicates that one country shares a land or maritime boundary directly with another country.
-
C.
hasBorderCity
chosen
Indicates that one location is a city situated on or very near the border of another geographic or political region.
-
D.
borderingRepublic
Indicates that one republic shares a land or maritime border with another republic.
-
E.
sharesInternationalBorderWith
Indicates that two geographic or political entities have a common boundary that is recognized as an international border.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e184ec8190aff3677c9b00a8f2 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:06 p.m.