Triple
T6256294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coco River |
E140173
|
entity |
| Predicate | formsNaturalBorder |
P17951
|
FINISHED |
| Object | between Nicaragua and Honduras |
—
|
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: between Nicaragua and Honduras | Statement: [Coco River, formsNaturalBorder, between Nicaragua and Honduras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsNaturalBorder Context triple: [Coco River, formsNaturalBorder, between Nicaragua and Honduras]
-
A.
formsEdgeOf
Indicates that one entity constitutes a boundary or outer limit of another entity.
-
B.
formsNaturalBarrierFor
Indicates that one entity physically obstructs or limits movement, access, or interaction for another entity by serving as a natural barrier.
-
C.
formsNaturalDivideBetween
chosen
Indicates that one entity serves as a natural boundary or separation between two other entities.
-
D.
formsNaturalRegionWith
Indicates that two or more geographic entities together constitute or belong to the same continuous natural region or landscape unit.
-
E.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063653910819095f1dc3b90ce77db |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.