Triple
T32742130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection |
E837243
|
entity |
| Predicate | associatedWithCatalogueNumber |
P85815
|
FINISHED |
| Object | Mahler Symphony No. 2 |
E139749
|
NE 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: Mahler Symphony No. 2 | Statement: [Resurrection, associatedWithCatalogueNumber, Mahler Symphony No. 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCatalogueNumber Context triple: [Resurrection, associatedWithCatalogueNumber, Mahler Symphony No. 2]
-
A.
cataloguedWith
Indicates that an item has been recorded, classified, or registered using a particular cataloging system, method, or identifier.
-
B.
alternativeCatalogNumber
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
C.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
workCatalogueNumber
chosen
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
E.
partOfWorkByCatalogueNumber
Indicates that an item is a component or section of a larger work, identified specifically by its catalogue number.
- F. None of above.
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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34b15a5b308190bd7d0ad4a44bdc9b |
completed | June 19, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:12 a.m.