Triple
T20801759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabula Rasa |
E512056
|
entity |
| Predicate | compositionTechnique |
P14965
|
FINISHED |
| Object | tintinnabuli |
—
|
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: tintinnabuli | Statement: [Tabula Rasa, compositionTechnique, tintinnabuli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionTechnique Context triple: [Tabula Rasa, compositionTechnique, tintinnabuli]
-
A.
specialEffectsTechnique
Indicates a relationship where a particular special effects method or process is used to create or enhance visual or auditory effects in a production.
-
B.
compositing
Indicates combining multiple visual elements or layers into a single cohesive image or scene.
-
C.
artisticTechnique
chosen
Indicates the method, style, or process used to create or execute an artistic work.
-
D.
coversTechnique
Indicates that one entity includes, addresses, or explains a particular technique within its scope or content.
-
E.
constructionTechniqueComparedTo
Indicates a relationship where one construction technique is evaluated or contrasted against another in terms of method, quality, efficiency, or other relevant criteria.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b0d75881909cc89ebe4e27adc1 |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:39 p.m.