Triple
T37890879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | río Putumayo |
E945131
|
entity |
| Predicate | formaFronteraEntre |
P224
|
FINISHED |
| Object | Colombia y Perú |
—
|
NE NERFINISHED |
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: Colombia y Perú | Statement: [río Putumayo, formaFronteraEntre, Colombia y Perú]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formaFronteraEntre Context triple: [río Putumayo, formaFronteraEntre, Colombia y Perú]
-
A.
borderedBy
chosen
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderCountrySide
Indicates that one country shares a land border with the side or region of another country.
-
C.
countryBorderType
Indicates the type or nature of the border relationship that exists between two countries.
-
D.
laterFormedBorderBetween
Indicates that the relationship or boundary between two entities was established at a later time, forming a border between them after an earlier period or state.
-
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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:19 p.m.