Triple
T28260161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organ Concerto in G minor |
E712560
|
entity |
| Predicate | hasOpusOrCatalogueDesignation |
P172221
|
FINISHED |
| Object | FP 93 |
—
|
NE NERFINISHED |
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: FP 93 | Statement: [Organ Concerto in G minor, hasOpusOrCatalogueDesignation, FP 93]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpusOrCatalogueDesignation Context triple: [Organ Concerto in G minor, hasOpusOrCatalogueDesignation, FP 93]
-
A.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
B.
cataloguedWithOpera
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
C.
cataloguedWith
chosen
Indicates that an item has been recorded, classified, or registered using a particular cataloging system, method, or identifier.
-
D.
hasCataloguedTitle
Indicates that an entity has a specific title recorded or listed in a catalog or cataloging system.
-
E.
collectionDesignation
Indicates that one entity assigns or specifies a particular collection label or designation for another entity.
- 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_69efb5207eb08190827e4c34048030b1 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 11:11 p.m.