Triple
T19221150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil–Peru border |
E480614
|
entity |
| Predicate | directionFromPeru |
P135034
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [Brazil–Peru border, directionFromPeru, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromPeru Context triple: [Brazil–Peru border, directionFromPeru, east]
-
A.
directionFromCusco
Indicates the cardinal or relative direction in which one entity is located from the reference point of Cusco.
-
B.
regionOnPeruSide
Indicates that a region is located on the side of a boundary or border that belongs to or is associated with Peru.
-
C.
directionFromSantiago
Indicates the cardinal or relative compass direction of an entity as measured from the location of Santiago.
-
D.
relativeLocationToUpperPeru
Indicates a spatial relationship specifying where something is located in relation to Upper Peru (e.g., north, south, adjacent to).
-
E.
directionFromBogotá
Indicates the cardinal or relative compass direction in which one place or object lies when measured from Bogotá.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:24 p.m.