Triple
T22384737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in A minor, Op. 4 No. 4, RV 356 |
E553365
|
entity |
| Predicate | setNumberWithinCollection |
P33773
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Violin Concerto in A minor, Op. 4 No. 4, RV 356, setNumberWithinCollection, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setNumberWithinCollection Context triple: [Violin Concerto in A minor, Op. 4 No. 4, RV 356, setNumberWithinCollection, 4]
-
A.
setsNumberOf
Indicates that one entity assigns or defines the numerical quantity or count associated with another entity.
-
B.
setNumbers
Indicates assigning or updating one or more numeric values associated with an entity or collection.
-
C.
positionInSet
chosen
Indicates that an entity occupies a specific position or rank within an ordered set or collection.
-
D.
numberWithinClass
Indicates that an entity has a specific numerical value or position that is defined relative to a particular class or category it belongs to.
-
E.
numberWithinSite
Indicates that an entity has a specific identifying number or position assigned within the context of a particular site or location.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582e58dc8190a2ad6b10c9d1f951 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.