Triple
T19221152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil–Peru border |
E480614
|
entity |
| Predicate | bordersPartOfPeru |
P91327
|
FINISHED |
| Object | eastern Peru |
—
|
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 Peru | Statement: [Brazil–Peru border, bordersPartOfPeru, eastern Peru]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersPartOfPeru Context triple: [Brazil–Peru border, bordersPartOfPeru, eastern Peru]
-
A.
regionOnPeruSide
chosen
Indicates that a region is located on the side of a boundary or border that belongs to or is associated with Peru.
-
B.
bordersVenezuelanState
Indicates that one entity shares a land or maritime boundary with a state within Venezuela.
-
C.
bordersNation
Indicates that one nation shares a land or maritime boundary with another nation.
-
D.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
E.
provinceBordering
Indicates that two provinces share a common boundary or border with each other.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa3fa9348190920f9d41b8beb900 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.