Triple
T22800871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in D minor, Op. 4 No. 8, RV 249 |
E564385
|
entity |
| Predicate | hasCollectionNumber |
P61667
|
FINISHED |
| Object | No. 8 in La stravaganza |
—
|
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. 8 in La stravaganza | Statement: [Violin Concerto in D minor, Op. 4 No. 8, RV 249, hasCollectionNumber, No. 8 in La stravaganza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollectionNumber Context triple: [Violin Concerto in D minor, Op. 4 No. 8, RV 249, hasCollectionNumber, No. 8 in La stravaganza]
-
A.
hasSeriesNumber
chosen
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
B.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
-
D.
hasEnsembleNumbers
Indicates that an entity is associated with one or more ensemble numbers used to identify it within a grouped or collective context.
-
E.
hasPicardNumber
Indicates that an entity (typically an algebraic variety) has a specified Picard number, i.e., the rank of its Picard group.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cdc72908190827c9e36a498dc97 |
completed | April 29, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:31 p.m.