Triple
T34043714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count M'Butu |
E873021
|
entity |
| Predicate | contributedStyle |
P145764
|
FINISHED |
| Object | Afro-Cuban influences |
—
|
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: Afro-Cuban influences | Statement: [Count M'Butu, contributedStyle, Afro-Cuban influences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributedStyle Context triple: [Count M'Butu, contributedStyle, Afro-Cuban influences]
-
A.
styleContribution
chosen
Indicates a relationship where one entity contributes to or influences the stylistic characteristics or aesthetic qualities of another.
-
B.
stylingContribution
Indicates a contribution made specifically to the styling, appearance, or visual presentation aspects of something.
-
C.
relatedStyle
Indicates that one style is associated with, similar to, or derived from another style in some relevant way.
-
D.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
E.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 1:51 a.m.