Triple
T14297939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CARICOM member state governments |
E354488
|
entity |
| Predicate | collectivelyImplement |
P83744
|
FINISHED |
| Object | CARICOM treaties |
—
|
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: CARICOM treaties | Statement: [CARICOM member state governments, collectivelyImplement, CARICOM treaties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectivelyImplement Context triple: [CARICOM member state governments, collectivelyImplement, CARICOM treaties]
-
A.
areImplementedBy
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
B.
implementedInCooperationWith
chosen
Indicates that an action, project, or initiative was carried out jointly or collaboratively together with another party.
-
C.
collectivelyAppoint
Indicates that multiple entities jointly decide on and designate someone or something to a role, position, or function.
-
D.
collectivelyAdopt
Indicates that multiple entities together choose, accept, or put into practice something as a group.
-
E.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
- 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_69d8278e17088190b328c5a9d4be74ff |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de717cfc948190ace5f1c91283b1c3 |
completed | April 14, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:11 a.m.