Triple
T25045610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ouanaminthe |
E627228
|
entity |
| Predicate | borderRiverNearby |
P150708
|
FINISHED |
| Object | Dajabón River |
—
|
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: Dajabón River | Statement: [Ouanaminthe, borderRiverNearby, Dajabón River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRiverNearby Context triple: [Ouanaminthe, borderRiverNearby, Dajabón River]
-
A.
borderingCountryNearby
Indicates that one country is geographically close to, but does not necessarily share a direct land border with, another country.
-
B.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
C.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
D.
borderRiverContext
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
-
E.
isOnBorderRiver
chosen
Indicates that something is located along or directly adjacent to a river that forms a border between areas.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:08 a.m.