Triple
T34753630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CUC$ |
E1001854
|
entity |
| Predicate | discontinuedInCountry |
P1466
|
FINISHED |
| Object | Cuba |
—
|
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: Cuba | Statement: [CUC$, discontinuedInCountry, Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discontinuedInCountry Context triple: [CUC$, discontinuedInCountry, Cuba]
-
A.
discontinuedIn
chosen
Indicates that an item, product, or service stopped being produced, offered, or supported starting in a specified time or place.
-
B.
discontinuedWith
Indicates that an item, service, or process has been stopped or terminated in association with a particular entity, condition, or context.
-
C.
discontinuationDateNorthAmerica
Indicates the date on which something stops being available or in use specifically within North America.
-
D.
discontinuedInVersionOf
Indicates that something (such as a feature, product, or component) ceased to be available or supported starting from a specific version of another entity.
-
E.
discontinuationAnnouncedBy
Indicates that an entity’s discontinuation (e.g., of a product, service, or activity) has been formally announced by a specific agent or organization.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 3:59 p.m.