Triple
T28793132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Miguel, Putumayo |
E727010
|
entity |
| Predicate | borderDepartment |
P194175
|
FINISHED |
| Object | Sucumbíos Province, Ecuador |
E297189
|
NE 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: Sucumbíos Province, Ecuador | Statement: [San Miguel, Putumayo, borderDepartment, Sucumbíos Province, Ecuador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDepartment Context triple: [San Miguel, Putumayo, borderDepartment, Sucumbíos Province, Ecuador]
-
A.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
C.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
D.
borderStationFor
Indicates that a particular border station serves, monitors, or is responsible for a specific border crossing or boundary segment.
-
E.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
- F. None of above. chosen
Provenance (5 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24a2758f6881908880b5599a4bbb4f |
completed | June 6, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: April 28, 2026, 6:24 a.m.