Triple
T25755003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Venezuela |
E648570
|
entity |
| Predicate | maritimeBoundaryDisputeBetween |
P49394
|
FINISHED |
| Object | Venezuela |
—
|
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: Venezuela | Statement: [Gulf of Venezuela, maritimeBoundaryDisputeBetween, Venezuela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritimeBoundaryDisputeBetween Context triple: [Gulf of Venezuela, maritimeBoundaryDisputeBetween, Venezuela]
-
A.
borderDisputesWith
chosen
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
maritimeBoundarySettledBy
Indicates that the maritime boundary between two entities has been formally determined and agreed upon through a specific decision, treaty, or authoritative process.
-
C.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
D.
islandContested
Indicates that control or ownership of an island is disputed or contested between two or more parties.
-
E.
claimedAsTerritorialSeaBy
Indicates that a body of water is asserted by a state or authority to be part of its territorial sea.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f600c18a14819081b5914dd3b0f9cf |
completed | May 2, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 4:39 a.m.