Triple
T31984368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marowijne River |
E816677
|
entity |
| Predicate | borderDisputeArea |
P12818
|
FINISHED |
| Object | upper Marowijne / Lawa region |
—
|
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: upper Marowijne / Lawa region | Statement: [Marowijne River, borderDisputeArea, upper Marowijne / Lawa region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderDisputeArea Context triple: [Marowijne River, borderDisputeArea, upper Marowijne / Lawa region]
-
A.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderDisputeResolvedBy
Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
-
C.
borderWithTerritory
Indicates that one territory shares a common boundary or border with another territory.
-
D.
borderDisputeRelatedLanguage
Indicates a relationship where the language is associated with, used in, or relevant to a border dispute between entities.
-
E.
borderRegion
chosen
Indicates a region that lies along or near the boundary separating two distinct geographic or political 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: May 1, 2026, 12:12 a.m.