Triple
T25215884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Étang Saumâtre |
E631825
|
entity |
| Predicate | borderFeatureFor |
P38214
|
FINISHED |
| Object | Haiti–Dominican Republic border region |
—
|
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: Haiti–Dominican Republic border region | Statement: [Étang Saumâtre, borderFeatureFor, Haiti–Dominican Republic border region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderFeatureFor Context triple: [Étang Saumâtre, borderFeatureFor, Haiti–Dominican Republic border region]
-
A.
borderCharacteristic
chosen
Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
-
B.
borderRegion
Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
-
C.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
borderRegionOf
Indicates that one region lies along, touches, or forms part of the boundary of another region.
-
E.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 12:59 p.m.