Triple
T20401188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loma de Cabrera |
E500333
|
entity |
| Predicate | isPartOfBorderRegionBetween |
P12818
|
FINISHED |
| Object | Dominican Republic and Haiti |
—
|
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: Dominican Republic and Haiti | Statement: [Loma de Cabrera, isPartOfBorderRegionBetween, Dominican Republic and Haiti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfBorderRegionBetween Context triple: [Loma de Cabrera, isPartOfBorderRegionBetween, Dominican Republic and Haiti]
-
A.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
B.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
C.
isBorderMunicipality
Indicates that a municipality is located on or directly adjacent to the border of a larger administrative region, country, or jurisdiction.
-
D.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
E.
borderingCountryOfRegion
Indicates that a country shares a land or maritime border with a specified geographic region.
- 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_69e0b4a81bec8190b69adfdc1336a015 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6798e7a588190b60bd54260e540f4 |
completed | April 20, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:29 a.m.