Triple
T23412442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in G minor, Op. 4 No. 6, RV 316a |
E560110
|
entity |
| Predicate | hasWorkNumberInCollection |
P57122
|
FINISHED |
| Object | No. 6 |
—
|
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: No. 6 | Statement: [Violin Concerto in G minor, Op. 4 No. 6, RV 316a, hasWorkNumberInCollection, No. 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkNumberInCollection Context triple: [Violin Concerto in G minor, Op. 4 No. 6, RV 316a, hasWorkNumberInCollection, No. 6]
-
A.
hasWorkInCollection
Indicates that a work or item is included as part of a particular collection.
-
B.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
C.
workNumberInSet
chosen
Indicates that a particular work number belongs to, or is included within, a specified set of work numbers.
-
D.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
E.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5124a54819087a7ae2f8a5b3dc0 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.