Triple
T37890893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | río Putumayo |
E945131
|
entity |
| Predicate | tipoDeFrontera |
P58557
|
FINISHED |
| Object | frontera fluvial |
—
|
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: frontera fluvial | Statement: [río Putumayo, tipoDeFrontera, frontera fluvial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDeFrontera Context triple: [río Putumayo, tipoDeFrontera, frontera fluvial]
-
A.
countryBorderType
chosen
Indicates the type or nature of the border relationship that exists between two countries.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
borderingUnitType
Indicates that one unit is adjacent to another unit of a specified type along a shared boundary.
-
D.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
E.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.