Triple
T19221170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil–Peru border |
E480614
|
entity |
| Predicate | partOfLargerBorderSystem |
P101494
|
FINISHED |
| Object | Brazil’s international borders |
—
|
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: Brazil’s international borders | Statement: [Brazil–Peru border, partOfLargerBorderSystem, Brazil’s international borders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLargerBorderSystem Context triple: [Brazil–Peru border, partOfLargerBorderSystem, Brazil’s international borders]
-
A.
isPartOfLargerBoundary
chosen
Indicates that one boundary is contained within or forms a component of a larger encompassing boundary.
-
B.
formsPartOfBorderType
Indicates that one border type constitutes a component or segment of another, more comprehensive border type.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
E.
hasBoundarySystem
Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
- 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.