Triple
T34745525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peru–Bolivia border |
E1001625
|
entity |
| Predicate | borderEstablishedYear |
P14619
|
FINISHED |
| Object | 1909 |
—
|
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: 1909 | Statement: [Peru–Bolivia border, borderEstablishedYear, 1909]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderEstablishedYear Context triple: [Peru–Bolivia border, borderEstablishedYear, 1909]
-
A.
borderEstablishedAfter
Indicates that a border between entities was created or formally established after a specified time or event.
-
B.
becameInternationalBorderInYear
Indicates that a boundary between entities started functioning as an international border in the specified year.
-
C.
borderEstablished
chosen
Indicates that a formal boundary between two geographic or political entities has been officially defined and put into effect.
-
D.
embassyYear
Indicates the year in which an embassy was established, opened, or became operational in relation to a particular country or location.
-
E.
borderTreatySignedOn
Indicates that a formal agreement establishing or modifying a border between entities was signed on a specific date.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 3:59 p.m.