Triple
T29989290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocifissione di sant'Andrea |
E761826
|
entity |
| Predicate | tecnica |
P3047
|
FINISHED |
| Object | olio su tela |
—
|
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: olio su tela | Statement: [Crocifissione di sant'Andrea, tecnica, olio su tela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tecnica Context triple: [Crocifissione di sant'Andrea, tecnica, olio su tela]
-
A.
featuresTechnique
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
B.
hasTechnique
chosen
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
C.
isTechnical
Indicates that an entity possesses specialized technical knowledge, skills, or characteristics related to technology, engineering, or applied sciences.
-
D.
technicalCrux
Indicates a key technical challenge or bottleneck that critically determines the feasibility or success of a solution or system.
-
E.
usedByTechnique
Indicates that a particular technique makes use of or employs the referenced entity as part of its method or process.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791985c08190815809bcc3258be8 |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:37 p.m.