Triple
T8520352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 3 in F minor, Op. 5 |
E201678
|
entity |
| Predicate | hasCatalogueAbbreviation |
P60896
|
FINISHED |
| Object | Op. 5 |
—
|
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: Op. 5 | Statement: [Piano Sonata No. 3 in F minor, Op. 5, hasCatalogueAbbreviation, Op. 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatalogueAbbreviation Context triple: [Piano Sonata No. 3 in F minor, Op. 5, hasCatalogueAbbreviation, Op. 5]
-
A.
catalogueAbbreviation
chosen
Indicates that one entity is used as the standardized abbreviated form of another entity within a catalogue or cataloging system.
-
B.
hasAbbreviationStatus
Indicates that an entity has a particular status or condition regarding its abbreviation (e.g., whether it is abbreviated, how, or to what extent).
-
C.
hasNameAbbreviation
Indicates that an entity is associated with a shortened or abbreviated form of its full name.
-
D.
isAbbreviation
Indicates that one term is a shortened or abbreviated form of another term.
-
E.
hasAbbreviationPattern
Indicates that there is a systematic abbreviation relationship between two strings, where one follows a recognizable pattern derived from the other.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.