Triple
T28726146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina and Bolivia |
E730228
|
entity |
| Predicate | borderCurrentStatus |
P138718
|
FINISHED |
| Object | internationally recognized |
—
|
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: internationally recognized | Statement: [Argentina and Bolivia, borderCurrentStatus, internationally recognized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderCurrentStatus Context triple: [Argentina and Bolivia, borderCurrentStatus, internationally recognized]
-
A.
boundaryStatus
chosen
Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
-
B.
borderCityStatus
Indicates that a city holds a designated status due to its location on or near a political or geographic border.
-
C.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
D.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
-
E.
boundaryCurrentOf
Indicates that one entity represents the current or present form/state of a boundary that is associated with or derived from another 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
Created at: April 28, 2026, 5:56 a.m.