Triple
T34334710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdelazer, or The Moor's Revenge |
E881112
|
entity |
| Predicate | musicCatalogNumber |
P84753
|
FINISHED |
| Object | Z 570 |
—
|
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: Z 570 | Statement: [Abdelazer, or The Moor's Revenge, musicCatalogNumber, Z 570]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicCatalogNumber Context triple: [Abdelazer, or The Moor's Revenge, musicCatalogNumber, Z 570]
-
A.
recordLabelCatalogNumber
Indicates the catalog or identification number assigned to a release by a record label.
-
B.
alternativeCatalogNumber
chosen
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
-
C.
musicAlbum
Indicates that there is a relationship where an entity is a music album associated with another entity, such as an artist or release.
-
D.
catalogueNumberForArtist
Indicates that a specific catalogue number is assigned to or associated with a particular artist.
-
E.
musicalWork
Indicates a relationship where an entity is identified as a musical composition or piece associated with another entity (such as a creator, performance, or recording).
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 1:58 a.m.