Triple
T22073070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il cimento dell’armonia e dell’inventione |
E545456
|
entity |
| Predicate | usesSoloTuttiContrast |
P146514
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Il cimento dell’armonia e dell’inventione, usesSoloTuttiContrast, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSoloTuttiContrast Context triple: [Il cimento dell’armonia e dell’inventione, usesSoloTuttiContrast, true]
-
A.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
B.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
C.
themeContrast
Indicates a relationship where two themes are compared or opposed to highlight their differences or tension.
-
D.
createsContrastIn
Indicates a relationship where one element is used to highlight or emphasize differences with another element within a given context.
-
E.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12889f504819089830202e64d97b0 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad59ef48190b62a2af636918a15 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.