Triple
T22196569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in E minor, Op. 4 No. 2, RV 279 |
E548564
|
entity |
| Predicate | RVNumber |
P146798
|
FINISHED |
| Object | RV 279 |
—
|
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: RV 279 | Statement: [Violin Concerto in E minor, Op. 4 No. 2, RV 279, RVNumber, RV 279]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RVNumber Context triple: [Violin Concerto in E minor, Op. 4 No. 2, RV 279, RVNumber, RV 279]
-
A.
RVNumberRange
Indicates that a recreational vehicle’s number or identifier falls within a specified numeric range.
-
B.
registrationNumber
Indicates the unique identifier assigned to an entity as part of an official or formal registration process.
-
C.
ringNumber
Indicates that an entity is assigned a specific ring identifier or position number within a ring-structured system or sequence.
-
D.
carNumberUsed
Indicates that a specific car number has been used or assigned in a given context or event.
-
E.
notableVehicleNumber
Indicates that a specific vehicle is identified as notable or significant by a particular number or identifier.
- F. None of above. chosen
Provenance (4 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.