Triple
T29631840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Santo Domingo |
E755592
|
entity |
| Predicate | isOnRiverMouth |
P124067
|
FINISHED |
| Object | Ozama 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: Ozama River | Statement: [Port of Santo Domingo, isOnRiverMouth, Ozama River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRiverMouth Context triple: [Port of Santo Domingo, isOnRiverMouth, Ozama River]
-
A.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
B.
isTidalMouthOf
Indicates that one location is the tidal mouth or estuarine outlet through which a river or watercourse enters a larger body of water.
-
C.
isOnRiverIsland
Indicates that one entity (typically a place or structure) is located on an island situated within a river.
-
D.
riverMouthAt
chosen
Indicates that the mouth or endpoint of a river is located at a specified place or geographic feature.
-
E.
isOnBorderRiver
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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f66e66da1081909f7f78f94232cbba |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:41 p.m.