Triple
T31358773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I. Introduzione e Allegro |
E799806
|
entity |
| Predicate | workOpusContext |
P144725
|
FINISHED |
| Object | part of Op. 29 |
—
|
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: part of Op. 29 | Statement: [I. Introduzione e Allegro, workOpusContext, part of Op. 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOpusContext Context triple: [I. Introduzione e Allegro, workOpusContext, part of Op. 29]
-
A.
workOpus
Indicates that an entity is the creator or author of a particular work or opus.
-
B.
workFromOpera
Indicates that an entity performs work or operates starting from, or based in, an opera-related context or location.
-
C.
workWithin
chosen
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
D.
workScope
Indicates the defined range, extent, and boundaries of tasks or responsibilities involved in a particular work activity or project.
-
E.
workWith
Indicates that one entity collaborates or engages in work-related activities together 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f4900b88190872299a7ec7e7674 |
completed | May 3, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.