Triple
T13995247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Issues |
E336677
|
entity |
| Predicate | singleNumberInArtistCareer |
P79254
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Issues, singleNumberInArtistCareer, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: singleNumberInArtistCareer Context triple: [Issues, singleNumberInArtistCareer, 3]
-
A.
isSoloDebutOf
Indicates that an event, work, or performance is the first solo appearance or release of a particular individual.
-
B.
hasSoloCareer
Indicates that an individual has pursued a musical or artistic career independently, separate from any group or band affiliations.
-
C.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
D.
firstNumberOneSingleForArtistInUK
chosen
Indicates that the artist has exactly one single that reached number one on the charts in the UK.
-
E.
significantPlaceInArtistCareer
Indicates that a place played an important or influential role in the course of an artist's professional 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb53f508190855cd69b8061dd77 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.