Triple
T2715848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuba (maritime boundary) |
E59963
|
entity |
| Predicate | delimits |
P1175
|
FINISHED |
| Object | Cuban territorial waters |
—
|
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: Cuban territorial waters | Statement: [Cuba (maritime boundary), delimits, Cuban territorial waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delimits Context triple: [Cuba (maritime boundary), delimits, Cuban territorial waters]
-
A.
separates
chosen
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
B.
alternativeDelimiters
Indicates a relationship where one or more substitute boundary markers are used in place of the primary delimiters for separating or enclosing elements.
-
C.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
D.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
E.
blockDelimiter
Indicates that one entity serves as a boundary marker that starts, ends, or separates a logical block associated with another entity.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda94d3288190bd60bc886e2106c7 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.