Triple
T29530143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All Things Majestic |
E749176
|
entity |
| Predicate | hasComposerEra |
P148815
|
FINISHED |
| Object | contemporary |
—
|
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: contemporary | Statement: [All Things Majestic, hasComposerEra, contemporary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerEra Context triple: [All Things Majestic, hasComposerEra, contemporary]
-
A.
associatedWithComposerEra
chosen
Indicates a relationship where a composer is linked to a particular historical musical era or stylistic period.
-
B.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
C.
hasPublicationEra
Indicates the time period or era during which a publication was released or made publicly available.
-
D.
hasCoComposer
Indicates that an entity shares authorship of a musical composition with one or more other composers.
-
E.
isFromArtistDebutEra
Indicates that the item is associated with the period corresponding to the artist’s debut era, such as their first major releases or initial phase of their career.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
Created at: April 28, 2026, 4:52 p.m.