Triple
T1231221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero (song) |
E26445
|
entity |
| Predicate | belongsToArtistDiscographyPeriod |
P10614
|
FINISHED |
| Object | early career |
—
|
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: early career | Statement: [Hero (song), belongsToArtistDiscographyPeriod, early career]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToArtistDiscographyPeriod Context triple: [Hero (song), belongsToArtistDiscographyPeriod, early career]
-
A.
chronologyWithinArtistOeuvre
chosen
Indicates the temporal ordering of works within a single artist’s body of work, specifying how one piece relates in time to others by the same artist.
-
B.
notableArtistInCollection
Indicates that an artist is prominently represented or recognized within a particular collection.
-
C.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
D.
musicBrainzArtist
Indicates a relationship where an entity is associated with a specific artist entry in the MusicBrainz database.
-
E.
hasArtist
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5a25348190a0665b6324c4d8f5 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.