Triple
T38273651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Cobre |
E1021282
|
entity |
| Predicate | patronessVenerated |
P190597
|
FINISHED |
| Object | patroness of Cuba |
—
|
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: patroness of Cuba | Statement: [El Cobre, patronessVenerated, patroness of Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronessVenerated Context triple: [El Cobre, patronessVenerated, patroness of Cuba]
-
A.
patroness
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
B.
patron of
Indicates a supportive relationship in which one entity provides sponsorship, protection, or backing to another, often enabling its activities or development.
-
C.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
D.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
E.
isVeneratedAs
Indicates that one entity is regarded and honored by others as sacred, holy, or worthy of deep reverence.
- F. None of above. chosen
Provenance (4 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.